AFS test automation report

Tests

scenarios for admin credentials and client credentials

3:38:22 pm / 02:05:47:758 Fail

scenarios for admin credentials and client credentials
04.04.2024 3:38:22 pm 04.04.2024 5:44:10 pm 02:05:47:758 · #test-id=1

PassTest scenario for verifing admin security scenario, to disable admin setting and verify in client side

PassTest scenario for verifing admin security scenario, to disable admin setting and verify in client side

Given User enters URL and is on login page for admin and client Test scenarios
SIGNIN BUTTON CLICKED

When User should land on landing page and verify
ADMIN PAGE HAS BEEN FOUND

Then User Clicks on Permissions by drop down to select Customer Account# for admin security
PERMISSION DROP DOWN HAS BEEN CLICKED, TO SELECT COMPANY

COMPANY HAS BEEN SELECTED

And User should enter menu "Security" in search bar and select "Permissions"
IN ADMIN PAGE

Then User searches for "Allow user to only modify contact information in Customer Master." "Allow user to modify Customer Master data." "Allow user to create new Customer Master data." and disable all of them
ADMIN SETTING ENTERED FOR SEARCH IS Allow user to only modify contact information in Customer Master.

VALUE SEARCHED HAS BEEN FOUND [[ChromeDriver: chrome on windows (fc75b255ed81f7c8870353a3c31386db)] -> xpath: //input[@class='k-checkbox']/ancestor::div[contains(@class,'admin-control-table')]/descendant::div[@class='label-containerX']]

CHECKBOX HAS BEEN UNCHECKED

ADMIN SETTING ENTERED FOR SEARCH IS Allow user to modify Customer Master data.

VALUE SEARCHED HAS BEEN FOUND [[ChromeDriver: chrome on windows (fc75b255ed81f7c8870353a3c31386db)] -> xpath: //input[@class='k-checkbox']/ancestor::div[contains(@class,'admin-control-table')]/descendant::div[@class='label-containerX']]

CHECKBOX HAS BEEN UNCHECKED

ADMIN SETTING ENTERED FOR SEARCH IS Allow user to create new Customer Master data.

VALUE SEARCHED HAS BEEN FOUND [[ChromeDriver: chrome on windows (fc75b255ed81f7c8870353a3c31386db)] -> xpath: //input[@class='k-checkbox']/ancestor::div[contains(@class,'admin-control-table')]/descendant::div[@class='label-containerX']]

CHECKBOX HAS BEEN UNCHECKED

And User logs out from Admin site, logs in to client credentials
SIGNIN BUTTON CLICKED

ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

USER ICON FOUND

IN ADMIN PAGE

Then User navigate to Client side
USER ICON FOUND

IN ADMIN PAGE

And User navigate to Customer Inq ERP env and Select Customer Account#
Customer #

CUSTOMER ACCOUNT DIALOG BOX HAS BEEN FOUND

PassTest scenario for verifing admin security scenario, to Enable admin setting and verify in client side

PassTest scenario for verifing admin security scenario, to Enable admin setting and verify in client side

Given User enters URL and is on login page for admin and client Test scenarios
SIGNIN BUTTON CLICKED

When User should land on landing page and verify
ADMIN PAGE HAS BEEN FOUND

Then User Clicks on Permissions by drop down to select Customer Account# for admin security
PERMISSION DROP DOWN HAS BEEN CLICKED, TO SELECT COMPANY

COMPANY HAS BEEN SELECTED

And User should enter menu "Security" in search bar and select "Permissions"
IN ADMIN PAGE

And User should enable all disabled admin settings "Allow user to only modify contact information in Customer Master." "Allow user to modify Customer Master data." "Allow user to create new Customer Master data."
ADMIN SETTING ENTERED FOR SEARCH IS Allow user to only modify contact information in Customer Master.

VALUE SEARCHED HAS BEEN FOUND [[ChromeDriver: chrome on windows (7a33c8aa83c8491caa0b252e6ebe3501)] -> xpath: //input[@class='k-checkbox']/ancestor::div[contains(@class,'admin-control-table')]/descendant::div[@class='label-containerX']]

CHECKBOX HAS NOT BEEN FOUND

ADMIN SETTING ENTERED FOR SEARCH IS Allow user to modify Customer Master data.

VALUE SEARCHED HAS BEEN FOUND [[ChromeDriver: chrome on windows (7a33c8aa83c8491caa0b252e6ebe3501)] -> xpath: //input[@class='k-checkbox']/ancestor::div[contains(@class,'admin-control-table')]/descendant::div[@class='label-containerX']]

CHECKBOX HAS NOT BEEN FOUND

ADMIN SETTING ENTERED FOR SEARCH IS Allow user to create new Customer Master data.

VALUE SEARCHED HAS BEEN FOUND [[ChromeDriver: chrome on windows (7a33c8aa83c8491caa0b252e6ebe3501)] -> xpath: //input[@class='k-checkbox']/ancestor::div[contains(@class,'admin-control-table')]/descendant::div[@class='label-containerX']]

CHECKBOX HAS NOT BEEN FOUND

And User logs out from Admin site, logs in to client credentials
SIGNIN BUTTON CLICKED

ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

USER ICON FOUND

IN ADMIN PAGE

Then User navigate to Client side
USER ICON FOUND

IN ADMIN PAGE

And User navigate to Customer Inq ERP env and Select Customer Account#
Customer #

CUSTOMER ACCOUNT DIALOG BOX HAS BEEN FOUND

Then User navigate to main tab and verify Primary contact has been editable
ALL PRIMARY CONTACT DETAILS ARE ENABLED

PassTest scenario for validating Catalog is loading automatically or not

PassTest scenario for validating Catalog is loading automatically or not

Given User should verify admin setting "Do not load full catalog search automatically" is enabled by using "CPCatalogDoNotAutoLoad"
ADMIN SETTING FOUND IS1

FOR ADMIN SETTING Do not load full catalog search automatically CHANGES

ADMIN SETTING IS ALREADY ENABLED

Then User enters URL and is on login page and entered credentials for admin setting
SIGNIN BUTTON CLICKED

When User is on Home Page
ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

Then User navigate to Client side
USER ICON FOUND

IN ADMIN PAGE

Then User should select Order Entry tab for Catalog for admin setting
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderEntry.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

NAVIGATED TO ORDER ENTRY PAGE

Then User selects Account# for Catalog for admin setting
CUSTOMER ACCOUNT# SELECTED IS K12958

DELIBERY DATE FOUND, AFTER LOGGING IN TO APPLICATION Friday, April 5, 2024

And User should navigate to Catalog tab for admin setting
CATALOG PAGE HAS BEEN FOUND

https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpProductCatalog.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

Then User verifies whether products are getting loaded automatically or not in catalog enabled setting
PRODUCTS ARE NOT LOADED AUTOMATICALLY, WE NEED TO CLICK ON RESET FILTER

Then User sign out from client side for Admin setting changes

And User should disable admin setting "Do not load full catalog search automatically" using "CPCatalogDoNotAutoLoad"
ADMIN SETTING IS DISABLED

FOR ADMIN SETTING Do not load full catalog search automatically CHANGES

ADMIN SETTING IS DISABLED

Then User enters URL and is on login page and entered credentials for admin setting
SIGNIN BUTTON CLICKED

When User is on Home Page for Admin setting for catalog
ADMIN PAGE OR PRODUCT CATALOG PAGE HAS BEEN FOUND

Then User navigate to Client side
USER ICON FOUND

IN ADMIN PAGE

Then User should select Order Entry tab for Catalog for admin setting
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderEntry.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

NAVIGATED TO ORDER ENTRY PAGE

Then User selects Account# for Catalog for admin setting
CUSTOMER ACCOUNT# SELECTED IS K12958

And User should navigate to Catalog tab for admin setting
CATALOG PAGE HAS BEEN FOUND

https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpProductCatalog.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

Then User verifies whether products are getting loaded automatically or not in catalog disabled setting
PRODUCTS ARE NOT LOADED AUTOMATICALLY, WE NEED TO CLICK ON RESET FILTER

Then User sign out from client side for Admin setting changes

And User should set admin setting "Do not load full catalog search automatically" "CPCatalogDoNotAutoLoad" as default before making changes
1 WHAT WAS THE PREVIOUS VALUE FOR ADMIN SETTING, AND CURRENT STATUS IS 0

ADMIN SETTING IS ENABLED

FOR ADMIN SETTING Do not load full catalog search automatically CHANGES

ADMIN SETTING IS DISABLED

PassTest scenario for validating Catalog is loading automatically or not

Given User should verify admin setting "Do not load full catalog automatically" is disabled by using "CPCatalogSearchDoNotAutoLoad"
FOR ADMIN SETTING Do not load full catalog automatically CHANGES

ADMIN SETTING IS ALREADY DISABLED

Then User enters URL and is on login page and entered credentials for admin setting
SIGNIN BUTTON CLICKED

When User is on Home Page
ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

Then User navigate to Client side
USER ICON FOUND

IN ADMIN PAGE

Then User should select Order Entry tab for Inventory for admin setting
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderEntry.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

NAVIGATED TO ORDER ENTRY PAGE

Then User selects Account# for Inventory for admin setting
CUSTOMER ACCOUNT# SELECTED IS K12958

And User should navigate to Inventory tab for admin setting

And User should click on Add product button and validate automatic load of products in product dialog box disabled
PRODUCT DIALOG HAS BEEN FOUND

CATALOG IN THE FORM OF LIST VIEW HAS BEEN FOUND

DO NOT AUTOLOAD CATALOG, IS DISABLED

Then User sign out from client side for Admin setting changes

And User should disable admin setting "Do not load full catalog automatically" using "CPCatalogSearchDoNotAutoLoad"
FOR ADMIN SETTING Do not load full catalog automatically CHANGES

ADMIN SETTING IS ALREADY DISABLED

FailTest scenario for enabling Hide prices in offline mode

FailTest scenario for enabling Hide prices in offline mode

Given User should verify admin setting "Hide prices in offline mode" is enabled by using "CPHidePriceInOfflineMode"
ADMIN SETTING FOUND IS0

ADMIN SETTING IS ENABLED

FOR ADMIN SETTING Hide prices in offline mode CHANGES

ADMIN SETTING IS ENABLED

When User enters URL and is on login page and entered credentials for admin setting
SIGNIN BUTTON CLICKED

When User is on Home Page for DM
ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

Then User navigate to Client side for DM
USER ICON FOUND

IN ADMIN PAGE

Then User should select Order Entry tab for DM
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderEntry.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

NAVIGATED TO ORDER ENTRY PAGE

When User Clicks on network symbol and click on taggle button to navigate to disconnected mode

And Then User selects Go offline option in Disconnected mode popup

Then User should get Customer account# popup

And User should select Customer Account# from popup and select the delivery date from popup wait till synchronized
DELIVERY DATE POPUP HAS BEEN FOUND

DELIVERY DATE HAS BEEN SELECTED

Then User must be on Order Entry Page in disconnected mode
USER IS ON DISCONNECTED MODE

Then User must click Start Order button
NAVIGATED TO ORDER ENTRY PAGE

ROUTE HAS DIALOG BOX HAS BEEN FOUND

SEARCH SCENARIO FOR ROUTECode AND 504

ROUTE FOUND IN INPUT BOX IS 504 - TRUCK 504

ROUTE SELECTED IS 504 - TRUCK 504

SUCCESSFULY SET THE ROUTE VALUE

START BUTTON HAS BEEN CLICKED

Then User should make selection between Pending order or Start New order

Then User should select Note from popup and Order guide from popup
ORDER GUIDE POPUP HAS BEEN FOUND

Then Enter PO# for New order
PO123

NEW ORDER ENTRY PAGE HAS BEEN FOUND

PO# ENTERED IS PO123

Then User enters Product# in Search box
PRODUCT SEARCHED USING SEARCH BAR IS 0046

Then Check for Catalog popup and check for price column in catalog in Disconnected mode
HIDE PRICE IN OFFLINE MODE IS ENABLED IN ADMIN, SO NO PRICE COLUMN SHOULD DISPLAY

java.lang.AssertionError: expected [false] but found [true] at org.testng.Assert.fail(Assert.java:97) at org.testng.Assert.assertEqualsImpl(Assert.java:136) at org.testng.Assert.assertEquals(Assert.java:118) at org.testng.Assert.assertEquals(Assert.java:751) at org.testng.Assert.assertEquals(Assert.java:761) at pages_DSD_OMS.orderEntry.NewOrderEntryPage.verifyNoPriceColumn(NewOrderEntryPage.java:5563) at stepDefination_DSD_OMS.AdminToClientNavigationSteps.AdminDisconnectedModeStep.checkForCatalogPopupAndCheckForPriceColumnInCatalogInDisconnectedMode(AdminDisconnectedModeStep.java:41) at ✽.Check for Catalog popup and check for price column in catalog in Disconnected mode(file:///C:/Users/Divya.Ramadas/Documents/Ign/AFS_Automation/OMS_Automation/src/test/resources/features_DSD_OMS/AdminToClientNavigation/disconnectedModeAdminFeature.feature:23)

Then Enter the Qty in the Product grid Case and Unit
60 60

Step skipped

Then Click on Next button
Step skipped

And Click on SubmitOrder button
Step skipped

Then User should be navigated to Order Entry page
Step skipped

When User clicks on network symbol and click on taggle button drop down should appear
Step skipped

And Then User should Click on taggle button to go online
Step skipped

Then User sign out from client side for Admin setting changes
Step skipped

And User should set admin setting "Hide prices in offline mode" "CPHidePriceInOfflineMode" as default before making changes
Step skipped

stepDefination_DSD_OMS.LoginPageStep.afterScenario1(io.cucumber.java.Scenario)
Test scenario for enabling Hide prices in offline mode
base64 img

FailTest scenario for disabling Hide prices in offline mode

FailTest scenario for disabling Hide prices in offline mode

Given User should verify admin setting "Hide prices in offline mode" is disabled by using "CPHidePriceInOfflineMode"
ADMIN SETTING IS DISABLED

FOR ADMIN SETTING Hide prices in offline mode CHANGES

ADMIN SETTING IS DISABLED

When User enters URL and is on login page and entered credentials for admin setting
SIGNIN BUTTON CLICKED

When User is on Home Page for DM

Then User navigate to Client side for DM

Then User should select Order Entry tab for DM

When User Clicks on network symbol and click on taggle button to navigate to disconnected mode

And Then User selects Go offline option in Disconnected mode popup

Then User should get Customer account# popup

And User should select Customer Account# from popup and select the delivery date from popup wait till synchronized

Then User must be on Order Entry Page in disconnected mode
IN ADMIN PAGE

https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderEntry.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

NAVIGATED TO ORDER ENTRY PAGE

CUSTOMER ACCOUNT# SELECTED IS K12958

java.lang.AssertionError: expected [true] but found [false] at org.testng.Assert.fail(Assert.java:97) at org.testng.Assert.assertEqualsImpl(Assert.java:136) at org.testng.Assert.assertEquals(Assert.java:118) at org.testng.Assert.assertEquals(Assert.java:751) at org.testng.Assert.assertEquals(Assert.java:761) at pages_DSD_OMS.disconnectedMode.DMOEPage.ValidateDisconnectedMode(DMOEPage.java:395) at stepDefination_DSD_OMS.DiconnectModePageSteps.DMOEPageStep.userMustBeOnOrderEntryPageInDisconnectedMode(DMOEPageStep.java:178) at ✽.User must be on Order Entry Page in disconnected mode(file:///C:/Users/Divya.Ramadas/Documents/Ign/AFS_Automation/OMS_Automation/src/test/resources/features_DSD_OMS/AdminToClientNavigation/disconnectedModeAdminFeature.feature:48)

Then User must click Start Order button
Step skipped

Then User should make selection between Pending order or Start New order
Step skipped

Then User should select Note from popup and Order guide from popup
Step skipped

Then Enter PO# for New order
PO123

Step skipped

Then User enters Product# in Search box
Step skipped

Then Check for Catalog popup and check for price column existence in catalog in Disconnected mode
Step skipped

Then Enter the Qty in the Product grid Case and Unit
60 60

Step skipped

Then Click on Next button
Step skipped

And Click on SubmitOrder button
Step skipped

Then User should be navigated to Order Entry page
Step skipped

When User clicks on network symbol and click on taggle button drop down should appear
Step skipped

And Then User should Click on taggle button to go online
Step skipped

Then User sign out from client side for Admin setting changes
Step skipped

And User should set admin setting "Hide prices in offline mode" "CPHidePriceInOfflineMode" as default before making changes
Step skipped

stepDefination_DSD_OMS.LoginPageStep.afterScenario1(io.cucumber.java.Scenario)
Test scenario for disabling Hide prices in offline mode
base64 img

PassTest scenario for enabled admin setting and verifying catalog dialog box is loaded with products

PassTest scenario for enabled admin setting and verifying catalog dialog box is loaded with products

Given User should verify admin setting "Do not load full catalog automatically" is enabled by using "CPCatalogSearchDoNotAutoLoad"
ADMIN SETTING FOUND IS0

ADMIN SETTING IS ENABLED

FOR ADMIN SETTING Do not load full catalog automatically CHANGES

ADMIN SETTING IS ENABLED

Then User enters URL and is on login page and entered credentials for admin setting
SIGNIN BUTTON CLICKED

When User is on Home Page
ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

Then User navigate to Client side
USER ICON FOUND

IN ADMIN PAGE

Then User should select Order Entry tab for Inventory for admin setting
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderEntry.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

NAVIGATED TO ORDER ENTRY PAGE

Then User selects Account# for Inventory for admin setting
CUSTOMER ACCOUNT# SELECTED IS K12958

And User should navigate to Inventory tab for admin setting

And User should click on Add product button and validate automatic load of products in product dialog box enabled
PRODUCT DIALOG HAS BEEN FOUND

CATALOG IN THE FORM OF LIST VIEW HAS BEEN FOUND

DO NOT AUTOLOAD CATALOG, IS DISABLED

PRODUCTS HAS BEEN SUCCESSFULLY LOADED AFTER CLICKING LOAD PRODUCTS

Then User sign out from client side for Admin setting changes

And User should set admin setting "Do not load full catalog automatically" "CPCatalogSearchDoNotAutoLoad" as default before making changes
0 WHAT WAS THE PREVIOUS VALUE FOR ADMIN SETTING, AND CURRENT STATUS IS 1

ADMIN SETTING IS DISABLED

FOR ADMIN SETTING Do not load full catalog automatically CHANGES

ADMIN SETTING IS ENABLED

PassTest scenario for verifying functionality of Non Presence of Sales help

PassTest scenario for verifying functionality of Non Presence of Sales help

Given User should verify admin setting "For disabling Sales help" is disabled by using "CPMasterNotificationsSalesHelp"
ADMIN SETTING IS DISABLED

FOR ADMIN SETTING For disabling Sales help CHANGES

ADMIN SETTING IS DISABLED

When User enters URL and is on login page and entered credentials for admin setting
SIGNIN BUTTON CLICKED

When User is on Home Page for sales help
ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

Then User navigate to Client side for sales help
USER ICON FOUND

IN ADMIN PAGE

Then User should select Order Entry tab for sales help
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderEntry.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

NAVIGATED TO ORDER ENTRY PAGE

And User click on Question mark and should validate no sales help option displayed

Then User sign out from client side for Admin setting changes

And User should set admin setting "For disabling Sales help" "CPMasterNotificationsSalesHelp" as default before making changes
1 WHAT WAS THE PREVIOUS VALUE FOR ADMIN SETTING, AND CURRENT STATUS IS 0

ADMIN SETTING IS ENABLED

FOR ADMIN SETTING For disabling Sales help CHANGES

ADMIN SETTING IS DISABLED

PassTest scenario for verifying functionality of Non Presence of eCommerce

PassTest scenario for verifying functionality of Non Presence of eCommerce

Given User should verify admin setting "For disabling eCommerce help" is disabled by using "CPMasterNotificationsHelp"
ADMIN SETTING IS DISABLED

FOR ADMIN SETTING For disabling eCommerce help CHANGES

ADMIN SETTING IS DISABLED

When User enters URL and is on login page and entered credentials for admin setting
SIGNIN BUTTON CLICKED

When User is on Home Page for sales help
ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

Then User navigate to Client side for sales help
USER ICON FOUND

IN ADMIN PAGE

Then User should select Order Entry tab for sales help
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderEntry.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

NAVIGATED TO ORDER ENTRY PAGE

And User click on Question mark and should validate no ecomerce help option displayed

Then User sign out from client side for Admin setting changes

And User should set admin setting "For disabling eCommerce help" "CPMasterNotificationsHelp" as default before making changes
1 WHAT WAS THE PREVIOUS VALUE FOR ADMIN SETTING, AND CURRENT STATUS IS 0

ADMIN SETTING IS ENABLED

FOR ADMIN SETTING For disabling eCommerce help CHANGES

ADMIN SETTING IS DISABLED

PassTest scenario for handling Sales help from drop down

PassTest scenario for handling Sales help from drop down

Given User should verify admin setting "For disabling Sales help" is enabled by using "CPMasterNotificationsSalesHelp"
ADMIN SETTING FOUND IS1

FOR ADMIN SETTING For disabling Sales help CHANGES

ADMIN SETTING IS ALREADY ENABLED

When User enters URL and is on login page and entered credentials for admin setting
SIGNIN BUTTON CLICKED

When User is on Home Page for sales help
ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

Then User navigate to Client side for sales help
USER ICON FOUND

IN ADMIN PAGE

Then User should select Order Entry tab for sales help
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderEntry.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

NAVIGATED TO ORDER ENTRY PAGE

And User click on Question mark and selects Sales help option
SALES HELP HAS BEEN HANDELED

Then User sign out from client side for Admin setting changes

And User should set admin setting "For disabling Sales help" "CPMasterNotificationsSalesHelp" as default before making changes
1 WHAT WAS THE PREVIOUS VALUE FOR ADMIN SETTING, AND CURRENT STATUS IS 1

PassTest scenario for handling eCommerce drop down

PassTest scenario for handling eCommerce drop down

Given User should verify admin setting "For disabling eCommerce help" is enabled by using "CPMasterNotificationsHelp"
ADMIN SETTING FOUND IS1

FOR ADMIN SETTING For disabling eCommerce help CHANGES

ADMIN SETTING IS ALREADY ENABLED

When User enters URL and is on login page and entered credentials for admin setting
SIGNIN BUTTON CLICKED

When User is on Home Page for sales help
ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

Then User navigate to Client side for eCommerce help
USER ICON FOUND

IN ADMIN PAGE

Then User should select Order Entry tab for eCommerce help
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderEntry.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

NAVIGATED TO ORDER ENTRY PAGE

And User click on Question mark and selects ecommerce option
eCOMMERCE HELP BUTTON HAS BEEN HANDLED

Then User sign out from client side for Admin setting changes

And User should set admin setting "For disabling eCommerce help" "CPMasterNotificationsHelp" as default before making changes
1 WHAT WAS THE PREVIOUS VALUE FOR ADMIN SETTING, AND CURRENT STATUS IS 1

PassTest scenario for verifying admin setting for OCL, For skip reason enable and disable

PassTest scenario for verifying admin setting for OCL, For skip reason enable and disable

Given User should verify admin setting "Require skip reason code" is disabled by using "CPOCLRequireSkipReason"
FOR ADMIN SETTING Require skip reason code CHANGES

ADMIN SETTING IS ALREADY DISABLED

Then User enters URL and is on login page and entered credentials for admin setting
SIGNIN BUTTON CLICKED

When User is on Home Page
ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

Then User navigate to Client side
USER ICON FOUND

IN ADMIN PAGE

Then User should select Order Entry tab for admin
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderEntry.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

NAVIGATED TO ORDER ENTRY PAGE

And User should navigate to OCL tab for admin setting
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderControlList.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

Then User should select Order taker from drop down

And Change the delivery date 2 days after current date
NAVIGATED TO ORDER CONTROL LIST

HAS BEEN SELECTED FOR OCL

Then User Clicks on Untaken radio button
NAVIGATED TO ORDER CONTROL LIST

Then User select OCL which is not skipped
CUSTOMER ACCOUNT NUMBER SELECTED FOR SKIP IS K00001

And User Clicks on Skip button
CUSTOMER ACCOUNT NUMBER SELECTED FOR SKIP IS K00001

Then User Clicks on Taken radio button
NAVIGATED TO ORDER CONTROL LIST

TAKEN RATIO BUTTON HAS BEEN SELECTED

And User verifies existence of customer account for which skip is enabled, exists under taken

Then User sign out from client side for Admin setting changes

And User should set admin setting "Require skip reason code" "CPOCLRequireSkipReason" as default before making changes
0 WHAT WAS THE PREVIOUS VALUE FOR ADMIN SETTING, AND CURRENT STATUS IS 0

PassTest scenario for verifying call desk existance

PassTest scenario for verifying call desk existance

Given User should verify admin setting "Call desk field" is disabled by using "CPEnableOCLCallDeskField"
ADMIN SETTING IS DISABLED

FOR ADMIN SETTING Call desk field CHANGES

ADMIN SETTING IS DISABLED

Then User enters URL and is on login page and entered credentials for admin setting
SIGNIN BUTTON CLICKED

When User is on Home Page
ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

Then User navigate to Client side
USER ICON FOUND

IN ADMIN PAGE

Then User should select Order Entry tab for admin
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderEntry.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

NAVIGATED TO ORDER ENTRY PAGE

And User should navigate to OCL tab for admin setting
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderControlList.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

Then User should select Order taker from drop down
ORDER TAKER HAS BEEN SELECTED

ORDER TAKER SELECTED IS BF, BRYAN FLINTOFF

And Change the delivery date 2 days after current date
NAVIGATED TO ORDER CONTROL LIST

HAS BEEN SELECTED FOR OCL

Then User validates existence of call desk input box for not displaying

Then User sign out from client side for Admin setting changes

And User should set admin setting "Call desk field" "CPEnableOCLCallDeskField" as default before making changes
1 WHAT WAS THE PREVIOUS VALUE FOR ADMIN SETTING, AND CURRENT STATUS IS 0

ADMIN SETTING IS ENABLED

FOR ADMIN SETTING Call desk field CHANGES

ADMIN SETTING IS DISABLED

PassTest scenario for verifying order taker admin setting

PassTest scenario for verifying order taker admin setting

Given User should verify admin setting "Order taker field" is disabled by using "CPEnableOCLOrderTakerField"
ADMIN SETTING IS DISABLED

FOR ADMIN SETTING Order taker field CHANGES

ADMIN SETTING IS DISABLED

Then User enters URL and is on login page and entered credentials for admin setting
SIGNIN BUTTON CLICKED

When User is on Home Page
ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

Then User navigate to Client side
USER ICON FOUND

IN ADMIN PAGE

Then User should select Order Entry tab for admin
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderEntry.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

NAVIGATED TO ORDER ENTRY PAGE

And User should navigate to OCL tab for admin setting
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderControlList.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

Then User should select Order taker from drop down

And Change the delivery date 2 days after current date
NAVIGATED TO ORDER CONTROL LIST

HAS BEEN SELECTED FOR OCL

Then User validates that Order taker drop down now displaying
NAVIGATED TO ORDER CONTROL LIST

Then User clicks on Print button and handle the new browser window
.pdf HAS BEEN FOUND

PRINT BUTTON IN OCL HAS BEEN HANDLED

Then User sign out from client side for Admin setting changes

And User should set admin setting "Order taker field" "CPEnableOCLOrderTakerField" as default before making changes
1 WHAT WAS THE PREVIOUS VALUE FOR ADMIN SETTING, AND CURRENT STATUS IS 0

ADMIN SETTING IS ENABLED

FOR ADMIN SETTING Order taker field CHANGES

ADMIN SETTING IS DISABLED

PassTest scenario for verifying order taker admin setting and verify route details in client side

PassTest scenario for verifying order taker admin setting and verify route details in client side

Given User should verify admin setting "Order taker field" is enabled by using "CPEnableOCLOrderTakerField"
ADMIN SETTING FOUND IS1

FOR ADMIN SETTING Order taker field CHANGES

ADMIN SETTING IS ALREADY ENABLED

Then User enters URL and is on login page and entered credentials for admin setting
SIGNIN BUTTON CLICKED

When User is on Home Page
ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

Then User navigate to Client side
USER ICON FOUND

IN ADMIN PAGE

Then User should select Order Entry tab for admin
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderEntry.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

NAVIGATED TO ORDER ENTRY PAGE

And User should navigate to OCL tab for admin setting
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderControlList.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

Then User validates that Order taker drop down now displaying
NAVIGATED TO ORDER CONTROL LIST

ORDER TAKER DROP DOWN IS DISPLAYED

Then User should select Order taker from drop down
ORDER TAKER HAS BEEN SELECTED

ORDER TAKER SELECTED IS BF, BRYAN FLINTOFF

And Change the delivery date 2 days after current date
NAVIGATED TO ORDER CONTROL LIST

HAS BEEN SELECTED FOR OCL

Then User enters Route# in Route search input box and count number of rows in OCL grid
ROUTE ENTERED FOR SEARCH: 705

NUMBER OF RECORDS FOUND FOR THE SELECTED ROUTE: 6

Then User sign out from client side for Admin setting changes

And User should set admin setting "Order taker field" "CPEnableOCLOrderTakerField" as default before making changes
1 WHAT WAS THE PREVIOUS VALUE FOR ADMIN SETTING, AND CURRENT STATUS IS 1

PassTest scenario for verifying order taker disabled in admin setting and verify route details in client side

PassTest scenario for verifying order taker disabled in admin setting and verify route details in client side

Given User should verify admin setting "Order taker field" is disabled by using "CPEnableOCLOrderTakerField"
ADMIN SETTING IS DISABLED

FOR ADMIN SETTING Order taker field CHANGES

ADMIN SETTING IS DISABLED

Then User enters URL and is on login page and entered credentials for admin setting
SIGNIN BUTTON CLICKED

When User is on Home Page
ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

Then User navigate to Client side
USER ICON FOUND

IN ADMIN PAGE

Then User should select Order Entry tab for admin
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderEntry.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

NAVIGATED TO ORDER ENTRY PAGE

And User should navigate to OCL tab for admin setting
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderControlList.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

Then User validates that Order taker drop down not displaying
NAVIGATED TO ORDER CONTROL LIST

And Change the delivery date 2 days after current date
NAVIGATED TO ORDER CONTROL LIST

HAS BEEN SELECTED FOR OCL

Then User enters Route# in Route search input box and count number of rows in OCL grid
NUMBER OF RECORDS FOUND FOR THE SELECTED ROUTE: 50

Then User sign out from client side for Admin setting changes

And User should set admin setting "Order taker field" "CPEnableOCLOrderTakerField" as default before making changes
1 WHAT WAS THE PREVIOUS VALUE FOR ADMIN SETTING, AND CURRENT STATUS IS 0

ADMIN SETTING IS ENABLED

FOR ADMIN SETTING Order taker field CHANGES

ADMIN SETTING IS DISABLED

FailTest scenario to verify functionality when orders exist before order submission is disabled

FailTest scenario to verify functionality when orders exist before order submission is disabled

Given User should verify admin setting "Validate if other orders exist before order submission" is disabled by using "CPValidateOtherOrdersBeforeSubmission"
ADMIN SETTING IS DISABLED

FOR ADMIN SETTING Validate if other orders exist before order submission CHANGES

ADMIN SETTING IS DISABLED

When User enters URL and is on login page and entered credentials for admin setting
SIGNIN BUTTON CLICKED

When User is on Home Page
ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

Then User navigate to Client side
USER ICON FOUND

IN ADMIN PAGE

Then User should select Order Entry tab for admin
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderEntry.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

NAVIGATED TO ORDER ENTRY PAGE

Then User selects Account# for Admin side setting
CUSTOMER ACCOUNT# SELECTED IS K12958

NAVIGATED TO ORDER ENTRY PAGE

Then User must click Start Order button
NAVIGATED TO ORDER ENTRY PAGE

START BUTTON HAS BEEN CLICKED

Then User should make selection between Pending order or Start New order

Then User should select Note from popup and Order guide from popup
ORDER GUIDE POPUP HAS BEEN FOUND

Then Enter PO# for New order
PO123

NEW ORDER ENTRY PAGE HAS BEEN FOUND

PO# ENTERED IS PO123

Then Enter Pro# in Quick Product Entry area

And Check for Case and Unit input box enabled or not based on that enter value
80 70

UOM IS ENABLED AND IT CONTAINS EA VALUE IN IT

UNIT ENTERED FOR QUICK PRODUCT IS 70

Then Click on Next button
PRODUCT FOUND IN ORDER ARE

java.lang.AssertionError: expected [true] but found [false] at org.testng.Assert.fail(Assert.java:97) at org.testng.Assert.assertEqualsImpl(Assert.java:136) at org.testng.Assert.assertEquals(Assert.java:118) at org.testng.Assert.assertEquals(Assert.java:751) at org.testng.Assert.assertEquals(Assert.java:761) at pages_DSD_OMS.orderEntry.NewOrderEntryPage.ClickNext(NewOrderEntryPage.java:813) at stepDefination_DSD_OMS.OrderEntryPageSteps.OrderEntryPageSteps.click_on_next_button(OrderEntryPageSteps.java:402) at ✽.Click on Next button(file:///C:/Users/Divya.Ramadas/Documents/Ign/AFS_Automation/OMS_Automation/src/test/resources/features_DSD_OMS/AdminToClientNavigation/orderEntryAdminToClientFeature.feature:21)

And Click on SubmitOrder button to verify Existing order dialog box
Step skipped

Then User should be navigated to Order Entry page
Step skipped

Then User sign out from client side for Admin setting changes
Step skipped

And User should set admin setting "Validate if other orders exist before order submission" "CPValidateOtherOrdersBeforeSubmission" as default before making changes
Step skipped

stepDefination_DSD_OMS.LoginPageStep.afterScenario1(io.cucumber.java.Scenario)
Test scenario to verify functionality when orders exist before order submission is disabled
base64 img

FailTest scenario to verify functionality when orders exist before order submission is enabled

FailTest scenario to verify functionality when orders exist before order submission is enabled

Given User should verify admin setting "Validate if other orders exist before order submission" is enabled by using "CPValidateOtherOrdersBeforeSubmission"
ADMIN SETTING FOUND IS0

ADMIN SETTING IS ENABLED

FOR ADMIN SETTING Validate if other orders exist before order submission CHANGES

ADMIN SETTING IS ENABLED

Then User enters URL and is on login page and entered credentials for admin setting
SIGNIN BUTTON CLICKED

When User is on Home Page
ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

Then User navigate to Client side
USER ICON FOUND

IN ADMIN PAGE

Then User should select Order Entry tab for admin
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderEntry.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

NAVIGATED TO ORDER ENTRY PAGE

Then User selects Account# for Admin side setting
CUSTOMER ACCOUNT# SELECTED IS K12958

NAVIGATED TO ORDER ENTRY PAGE

Then User must click Start Order button
NAVIGATED TO ORDER ENTRY PAGE

START BUTTON HAS BEEN CLICKED

Then User should make selection between Pending order or Start New order

Then User should select Note from popup and Order guide from popup
ORDER GUIDE POPUP HAS BEEN FOUND

Then Enter PO# for New order
PO123

NEW ORDER ENTRY PAGE HAS BEEN FOUND

PO# ENTERED IS PO123

Then Enter Pro# in Quick Product Entry area

And Check for Case and Unit input box enabled or not based on that enter value
80 70

UOM IS ENABLED AND IT CONTAINS EA VALUE IN IT

UNIT ENTERED FOR QUICK PRODUCT IS 70

Then Click on Next button
PRODUCT FOUND IN ORDER ARE

java.lang.AssertionError: expected [true] but found [false] at org.testng.Assert.fail(Assert.java:97) at org.testng.Assert.assertEqualsImpl(Assert.java:136) at org.testng.Assert.assertEquals(Assert.java:118) at org.testng.Assert.assertEquals(Assert.java:751) at org.testng.Assert.assertEquals(Assert.java:761) at pages_DSD_OMS.orderEntry.NewOrderEntryPage.ClickNext(NewOrderEntryPage.java:813) at stepDefination_DSD_OMS.OrderEntryPageSteps.OrderEntryPageSteps.click_on_next_button(OrderEntryPageSteps.java:402) at ✽.Click on Next button(file:///C:/Users/Divya.Ramadas/Documents/Ign/AFS_Automation/OMS_Automation/src/test/resources/features_DSD_OMS/AdminToClientNavigation/orderEntryAdminToClientFeature.feature:46)

And Click on SubmitOrder button to display of Existing order dialog box after enabling admin setting
Step skipped

Then User should be navigated to Order Entry page
Step skipped

Then User sign out from client side for Admin setting changes
Step skipped

And User should set admin setting "Validate if other orders exist before order submission" "CPValidateOtherOrdersBeforeSubmission" as default before making changes
Step skipped

stepDefination_DSD_OMS.LoginPageStep.afterScenario1(io.cucumber.java.Scenario)
Test scenario to verify functionality when orders exist before order submission is enabled
base64 img

FailTest scenario to verify functionality when orders exist before order submission is enabled and click on cancel button, in Order exists dialog box

FailTest scenario to verify functionality when orders exist before order submission is enabled and click on cancel button, in Order exists dialog box

Given User should verify admin setting "Validate if other orders exist before order submission" is enabled by using "CPValidateOtherOrdersBeforeSubmission"
ADMIN SETTING FOUND IS1

FOR ADMIN SETTING Validate if other orders exist before order submission CHANGES

ADMIN SETTING IS ALREADY ENABLED

Then User enters URL and is on login page and entered credentials for admin setting
SIGNIN BUTTON CLICKED

When User is on Home Page
ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

Then User navigate to Client side
USER ICON FOUND

IN ADMIN PAGE

Then User should select Order Entry tab for admin
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderEntry.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

NAVIGATED TO ORDER ENTRY PAGE

Then User selects Account# for Admin side setting
CUSTOMER ACCOUNT# SELECTED IS K12958

NAVIGATED TO ORDER ENTRY PAGE

Then User must click Start Order button
NAVIGATED TO ORDER ENTRY PAGE

START BUTTON HAS BEEN CLICKED

Then User should make selection between Pending order or Start New order

Then User should select Note from popup and Order guide from popup
ORDER GUIDE POPUP HAS BEEN FOUND

Then Enter PO# for New order
PO123

NEW ORDER ENTRY PAGE HAS BEEN FOUND

PO# ENTERED IS PO123

Then Enter Pro# in Quick Product Entry area

And Check for Case and Unit input box enabled or not based on that enter value
80 70

UOM IS ENABLED AND IT CONTAINS EA VALUE IN IT

UNIT ENTERED FOR QUICK PRODUCT IS 70

Then Click on Next button
PRODUCT FOUND IN ORDER ARE

java.lang.AssertionError: expected [true] but found [false] at org.testng.Assert.fail(Assert.java:97) at org.testng.Assert.assertEqualsImpl(Assert.java:136) at org.testng.Assert.assertEquals(Assert.java:118) at org.testng.Assert.assertEquals(Assert.java:751) at org.testng.Assert.assertEquals(Assert.java:761) at pages_DSD_OMS.orderEntry.NewOrderEntryPage.ClickNext(NewOrderEntryPage.java:813) at stepDefination_DSD_OMS.OrderEntryPageSteps.OrderEntryPageSteps.click_on_next_button(OrderEntryPageSteps.java:402) at ✽.Click on Next button(file:///C:/Users/Divya.Ramadas/Documents/Ign/AFS_Automation/OMS_Automation/src/test/resources/features_DSD_OMS/AdminToClientNavigation/orderEntryAdminToClientFeature.feature:71)

And Click on SubmitOrder button and click on cancel button when Order exists dialog box appears
Step skipped

Then User should be navigated to Order Entry page
Step skipped

Then User sign out from client side for Admin setting changes
Step skipped

And User should set admin setting "Validate if other orders exist before order submission" "CPValidateOtherOrdersBeforeSubmission" as default before making changes
Step skipped

stepDefination_DSD_OMS.LoginPageStep.afterScenario1(io.cucumber.java.Scenario)
Test scenario to verify functionality when orders exist before order submission is enabled and click on cancel button, in Order exists dialog box
base64 img

FailTest scenario to verify functionality when orders exist before order submission is enabled and click on No button, in Order exists dialog box

FailTest scenario to verify functionality when orders exist before order submission is enabled and click on No button, in Order exists dialog box

Given User should verify admin setting "Validate if other orders exist before order submission" is enabled by using "CPValidateOtherOrdersBeforeSubmission"
ADMIN SETTING FOUND IS1

FOR ADMIN SETTING Validate if other orders exist before order submission CHANGES

ADMIN SETTING IS ALREADY ENABLED

Then User enters URL and is on login page and entered credentials for admin setting
SIGNIN BUTTON CLICKED

When User is on Home Page
ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

Then User navigate to Client side
USER ICON FOUND

IN ADMIN PAGE

Then User should select Order Entry tab for admin
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderEntry.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

NAVIGATED TO ORDER ENTRY PAGE

Then User selects Account# for Admin side setting
CUSTOMER ACCOUNT# SELECTED IS K12958

NAVIGATED TO ORDER ENTRY PAGE

Then User must click Start Order button
NAVIGATED TO ORDER ENTRY PAGE

START BUTTON HAS BEEN CLICKED

Then User should make selection between Pending order or Start New order

Then User should select Note from popup and Order guide from popup
ORDER GUIDE POPUP HAS BEEN FOUND

Then Enter PO# for New order
PO123

NEW ORDER ENTRY PAGE HAS BEEN FOUND

PO# ENTERED IS PO123

Then Enter Pro# in Quick Product Entry area

And Check for Case and Unit input box enabled or not based on that enter value
80 70

UOM IS ENABLED AND IT CONTAINS EA VALUE IN IT

UNIT ENTERED FOR QUICK PRODUCT IS 70

Then Click on Next button
PRODUCT FOUND IN ORDER ARE

java.lang.AssertionError: expected [true] but found [false] at org.testng.Assert.fail(Assert.java:97) at org.testng.Assert.assertEqualsImpl(Assert.java:136) at org.testng.Assert.assertEquals(Assert.java:118) at org.testng.Assert.assertEquals(Assert.java:751) at org.testng.Assert.assertEquals(Assert.java:761) at pages_DSD_OMS.orderEntry.NewOrderEntryPage.ClickNext(NewOrderEntryPage.java:813) at stepDefination_DSD_OMS.OrderEntryPageSteps.OrderEntryPageSteps.click_on_next_button(OrderEntryPageSteps.java:402) at ✽.Click on Next button(file:///C:/Users/Divya.Ramadas/Documents/Ign/AFS_Automation/OMS_Automation/src/test/resources/features_DSD_OMS/AdminToClientNavigation/orderEntryAdminToClientFeature.feature:96)

And Click on SubmitOrder button and click on No button when Order exists dialog box appears
Step skipped

Then User should be navigated to Order Entry page
Step skipped

Then User sign out from client side for Admin setting changes
Step skipped

And User should set admin setting "Validate if other orders exist before order submission" "CPValidateOtherOrdersBeforeSubmission" as default before making changes
Step skipped

stepDefination_DSD_OMS.LoginPageStep.afterScenario1(io.cucumber.java.Scenario)
Test scenario to verify functionality when orders exist before order submission is enabled and click on No button, in Order exists dialog box
base64 img

FailTest scenario to verify functionality for enable admin setting for PO#

FailTest scenario to verify functionality for enable admin setting for PO#

Given User should verify admin setting "Input required for the PO# field" is enabled by using "CPRequirePONumber"
ADMIN SETTING FOUND IS0

ADMIN SETTING IS ENABLED

FOR ADMIN SETTING Input required for the PO# field CHANGES

ADMIN SETTING IS ENABLED

When User enters URL and is on login page and entered credentials for admin setting
SIGNIN BUTTON CLICKED

When User is on Home Page
ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

Then User navigate to Client side
USER ICON FOUND

IN ADMIN PAGE

Then User should select Order Entry tab for admin
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderEntry.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

NAVIGATED TO ORDER ENTRY PAGE

Then User selects Account# for Admin side setting
CUSTOMER ACCOUNT# SELECTED IS K12958

NAVIGATED TO ORDER ENTRY PAGE

Then User must click Start Order button
NAVIGATED TO ORDER ENTRY PAGE

START BUTTON HAS BEEN CLICKED

Then User should make selection between Pending order or Start New order

Then User should select Note from popup and Order guide from popup
ORDER GUIDE POPUP HAS BEEN FOUND

Then Enter PO# for New order and Po mandatory message should display
PO123

NEW ORDER ENTRY PAGE HAS BEEN FOUND

PO# IS MANDATORY MESSAGE HAS BEEN FOUND

PO# ENTERED IS PO123

Then Enter Pro# in Quick Product Entry area

And Check for Case and Unit input box enabled or not based on that enter value
80 70

UOM IS ENABLED AND IT CONTAINS EA VALUE IN IT

UNIT ENTERED FOR QUICK PRODUCT IS 70

Then Click on Next button
PRODUCT FOUND IN ORDER ARE

java.lang.AssertionError: expected [true] but found [false] at org.testng.Assert.fail(Assert.java:97) at org.testng.Assert.assertEqualsImpl(Assert.java:136) at org.testng.Assert.assertEquals(Assert.java:118) at org.testng.Assert.assertEquals(Assert.java:751) at org.testng.Assert.assertEquals(Assert.java:761) at pages_DSD_OMS.orderEntry.NewOrderEntryPage.ClickNext(NewOrderEntryPage.java:813) at stepDefination_DSD_OMS.OrderEntryPageSteps.OrderEntryPageSteps.click_on_next_button(OrderEntryPageSteps.java:402) at ✽.Click on Next button(file:///C:/Users/Divya.Ramadas/Documents/Ign/AFS_Automation/OMS_Automation/src/test/resources/features_DSD_OMS/AdminToClientNavigation/orderEntryAdminToClientFeature.feature:121)

And Click on SubmitOrder button
Step skipped

Then User should be navigated to Order Entry page
Step skipped

Then User sign out from client side for Admin setting changes
Step skipped

And User should set admin setting "Input required for the PO# field" "CPRequirePONumber" as default before making changes
Step skipped

stepDefination_DSD_OMS.LoginPageStep.afterScenario1(io.cucumber.java.Scenario)
Test scenario to verify functionality for enable admin setting for PO#
base64 img

FailTest scenario to verify functionality for disabled admin setting for PO#

FailTest scenario to verify functionality for disabled admin setting for PO#

Given User should verify admin setting "Input required for the PO# field" is disabled by using "CPRequirePONumber"
ADMIN SETTING IS DISABLED

FOR ADMIN SETTING Input required for the PO# field CHANGES

ADMIN SETTING IS DISABLED

When User enters URL and is on login page and entered credentials for admin setting
SIGNIN BUTTON CLICKED

When User is on Home Page
ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

Then User navigate to Client side
USER ICON FOUND

IN ADMIN PAGE

Then User should select Order Entry tab for admin
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderEntry.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

NAVIGATED TO ORDER ENTRY PAGE

Then User selects Account# for Admin side setting
CUSTOMER ACCOUNT# SELECTED IS K12958

NAVIGATED TO ORDER ENTRY PAGE

Then User must click Start Order button
NAVIGATED TO ORDER ENTRY PAGE

START BUTTON HAS BEEN CLICKED

Then User should make selection between Pending order or Start New order

Then User should select Note from popup and Order guide from popup
ORDER GUIDE POPUP HAS BEEN FOUND

Then Enter PO# for New order and Po mandatory message should not display
PO123

NEW ORDER ENTRY PAGE HAS BEEN FOUND

PO# IS MANDATORY MESSAGE HAS NOT BEEN FOUND

DO CHECK EVEN IN CUSTOMER INQ, ACCOUNT, PO# MANDATORY SETTING SHOULD BE SET TO NO

PO# ENTERED IS PO123

Then Enter Pro# in Quick Product Entry area

And Check for Case and Unit input box enabled or not based on that enter value
80 70

UOM IS ENABLED AND IT CONTAINS EA VALUE IN IT

UNIT ENTERED FOR QUICK PRODUCT IS 70

Then Click on Next button
PRODUCT FOUND IN ORDER ARE

java.lang.AssertionError: expected [true] but found [false] at org.testng.Assert.fail(Assert.java:97) at org.testng.Assert.assertEqualsImpl(Assert.java:136) at org.testng.Assert.assertEquals(Assert.java:118) at org.testng.Assert.assertEquals(Assert.java:751) at org.testng.Assert.assertEquals(Assert.java:761) at pages_DSD_OMS.orderEntry.NewOrderEntryPage.ClickNext(NewOrderEntryPage.java:813) at stepDefination_DSD_OMS.OrderEntryPageSteps.OrderEntryPageSteps.click_on_next_button(OrderEntryPageSteps.java:402) at ✽.Click on Next button(file:///C:/Users/Divya.Ramadas/Documents/Ign/AFS_Automation/OMS_Automation/src/test/resources/features_DSD_OMS/AdminToClientNavigation/orderEntryAdminToClientFeature.feature:146)

And Click on SubmitOrder button
Step skipped

Then User should be navigated to Order Entry page
Step skipped

Then User sign out from client side for Admin setting changes
Step skipped

And User should set admin setting "Input required for the PO# field" "CPRequirePONumber" as default before making changes
Step skipped

stepDefination_DSD_OMS.LoginPageStep.afterScenario1(io.cucumber.java.Scenario)
Test scenario to verify functionality for disabled admin setting for PO#
base64 img

PassTest scenario to disable Multiple orders per delivery day

PassTest scenario to disable Multiple orders per delivery day

Given User should verify admin setting "Multiple orders per delivery day" is disabled by using "CPEnableMultipleOrdersPerDay"
ADMIN SETTING IS DISABLED

FOR ADMIN SETTING Multiple orders per delivery day CHANGES

ADMIN SETTING IS DISABLED

When User enters URL and is on login page and entered credentials for admin setting
SIGNIN BUTTON CLICKED

When User is on Home Page
ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

Then User navigate to Client side
USER ICON FOUND

IN ADMIN PAGE

Then User should select Order Entry tab for admin
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderEntry.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

NAVIGATED TO ORDER ENTRY PAGE

Then User selects Account# for Admin side setting
CUSTOMER ACCOUNT# SELECTED IS K12958

NAVIGATED TO ORDER ENTRY PAGE

Then User must click Start Order button should be disabled
NAVIGATED TO ORDER ENTRY PAGE

MULTIPLE ORDERS PER DELIVERY DAY, IS DISABLED. AND WORKING AS EXPECTED

Then User sign out from client side for Admin setting changes

And User should set admin setting "Multiple orders per delivery day" "CPEnableMultipleOrdersPerDay" as default before making changes
1 WHAT WAS THE PREVIOUS VALUE FOR ADMIN SETTING, AND CURRENT STATUS IS 0

ADMIN SETTING IS ENABLED

FOR ADMIN SETTING Multiple orders per delivery day CHANGES

ADMIN SETTING IS DISABLED

FailTest scenario to enable multiple orders per delivery day

FailTest scenario to enable multiple orders per delivery day

Given User should verify admin setting "Multiple orders per delivery day" is enabled by using "CPEnableMultipleOrdersPerDay"
ADMIN SETTING FOUND IS1

FOR ADMIN SETTING Multiple orders per delivery day CHANGES

ADMIN SETTING IS ALREADY ENABLED

When User enters URL and is on login page and entered credentials for admin setting
SIGNIN BUTTON CLICKED

When User is on Home Page
ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

Then User navigate to Client side
USER ICON FOUND

IN ADMIN PAGE

Then User should select Order Entry tab for admin
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderEntry.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

NAVIGATED TO ORDER ENTRY PAGE

Then User selects Account# for Admin side setting
CUSTOMER ACCOUNT# SELECTED IS K12958

NAVIGATED TO ORDER ENTRY PAGE

Then User should check start order button enabled click Start Order button
NAVIGATED TO ORDER ENTRY PAGE

NUMBER OF ORDERS ALREADY CREATED ARE 6

ORDERS ARE:

1196632

1197060

1197061

1197062

1197063

1197064

MULTIPLE ORDERS PER DELIVERY DAY, IS ENABLED. AND WORKING AS EXPECTED

Then User should make selection between Pending order or Start New order

Then User should select Note from popup and Order guide from popup
ORDER GUIDE POPUP HAS BEEN FOUND

Then Enter PO# for New order
PO123

NEW ORDER ENTRY PAGE HAS BEEN FOUND

PO# ENTERED IS PO123

Then Enter Pro# in Quick Product Entry area

And Check for Case and Unit input box enabled or not based on that enter value
80 70

UOM IS ENABLED AND IT CONTAINS EA VALUE IN IT

UNIT ENTERED FOR QUICK PRODUCT IS 70

Then Click on Next button
PRODUCT FOUND IN ORDER ARE

java.lang.AssertionError: expected [true] but found [false] at org.testng.Assert.fail(Assert.java:97) at org.testng.Assert.assertEqualsImpl(Assert.java:136) at org.testng.Assert.assertEquals(Assert.java:118) at org.testng.Assert.assertEquals(Assert.java:751) at org.testng.Assert.assertEquals(Assert.java:761) at pages_DSD_OMS.orderEntry.NewOrderEntryPage.ClickNext(NewOrderEntryPage.java:813) at stepDefination_DSD_OMS.OrderEntryPageSteps.OrderEntryPageSteps.click_on_next_button(OrderEntryPageSteps.java:402) at ✽.Click on Next button(file:///C:/Users/Divya.Ramadas/Documents/Ign/AFS_Automation/OMS_Automation/src/test/resources/features_DSD_OMS/AdminToClientNavigation/orderEntryAdminToClientFeature.feature:186)

And Click on SubmitOrder button
Step skipped

Then User should be navigated to Order Entry page and display all orders created
Step skipped

Then User sign out from client side for Admin setting changes
Step skipped

And User should set admin setting "Multiple orders per delivery day" "CPEnableMultipleOrdersPerDay" as default before making changes
Step skipped

stepDefination_DSD_OMS.LoginPageStep.afterScenario1(io.cucumber.java.Scenario)
Test scenario to enable multiple orders per delivery day
base64 img

FailTest scenario for enable auto loading of products in catalog dialog box, in grid view

FailTest scenario for enable auto loading of products in catalog dialog box, in grid view

Given User enters URL and is on login page and entered credentials for Admin settings
SIGNIN BUTTON CLICKED

When User is on Home Page for Admin settings
ADMIN PAGE HAS BEEN FOUND

Then User Clicks on Permissions by drop down to select Customer Account#s
PERMISSION DROP DOWN HAS BEEN CLICKED, TO SELECT COMPANY

COMPANY HAS BEEN SELECTED

And User should enter menu "Catalog Search" in search bar to navigate to catalog search
IN ADMIN PAGE

USER IS ON CATALOG SEARCH

Then User should select "Grid layout" in Catalog search layout and enable Do not load full catalog automatically
DONOT AUTO LOAD PODUCT CATALOG ENABLED

DO NOT LOAD FULL CATALOG AUTOMATICALLY, IS ENABLED

And User should save all the details

And User logs out from Admin site, logs in to client credentials
SIGNIN BUTTON CLICKED

ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

USER ICON FOUND

IN ADMIN PAGE

When User is on Home Page
ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

Then User navigate to Client side
USER ICON FOUND

IN ADMIN PAGE

Then User should select Order Entry tab for admin
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderEntry.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

NAVIGATED TO ORDER ENTRY PAGE

Then User selects Account# for Admin side setting
CUSTOMER ACCOUNT# SELECTED IS K12958

NAVIGATED TO ORDER ENTRY PAGE

Then User must click Start Order button for Admin setting testing
NAVIGATED TO ORDER ENTRY PAGE

START BUTTON HAS BEEN CLICKED

Then User should make selection between Pending order or Start New order

Then User should select Note from popup and Order guide from popup
ORDER GUIDE POPUP HAS BEEN FOUND

Then Enter PO# for New order
PO123

NEW ORDER ENTRY PAGE HAS BEEN FOUND

PO# ENTERED IS PO123

Then Click on Add product drop down and select catalog option
ADD PRODUCT BUTTON HAS BEEN CLICKED

ADD PRODUCT FROM CATALOG IS SELECTED

And User should verify products are not auto loaded select Product from catalog and Enter Qty for the products
50 60

CATALOG DIALOG BOX HAS BEEN FOUND

DO NOT LOAD FULL CATALOG AUTOMATICALLY,HAS BEEN ENABLED

PORDUCT NUMBER ENERED IN INPUT BOX 0046

PORDUCT NUMBER ENERED IN INPUT BOX 0046

PRODUCT # 0046 PRODUCT QTY 50 60

Then Click on Next button
PRODUCT FOUND IN ORDER ARE

java.lang.AssertionError: expected [true] but found [false] at org.testng.Assert.fail(Assert.java:97) at org.testng.Assert.assertEqualsImpl(Assert.java:136) at org.testng.Assert.assertEquals(Assert.java:118) at org.testng.Assert.assertEquals(Assert.java:751) at org.testng.Assert.assertEquals(Assert.java:761) at pages_DSD_OMS.orderEntry.NewOrderEntryPage.ClickNext(NewOrderEntryPage.java:813) at stepDefination_DSD_OMS.OrderEntryPageSteps.OrderEntryPageSteps.click_on_next_button(OrderEntryPageSteps.java:402) at ✽.Click on Next button(file:///C:/Users/Divya.Ramadas/Documents/Ign/AFS_Automation/OMS_Automation/src/test/resources/features_DSD_OMS/AdminToClientNavigation/orderEntryAdminToClientFeature.feature:216)

And Click on SubmitOrder button
Step skipped

Then User should be navigated to Order Entry page
Step skipped

stepDefination_DSD_OMS.LoginPageStep.afterScenario1(io.cucumber.java.Scenario)
Test scenario for enable auto loading of products in catalog dialog box, in grid view
base64 img

FailTest scenario for disable auto loading of products in catalog dialog box, in grid view

FailTest scenario for disable auto loading of products in catalog dialog box, in grid view

Given User enters URL and is on login page and entered credentials for Admin settings
SIGNIN BUTTON CLICKED

When User is on Home Page for Admin settings
ADMIN PAGE HAS BEEN FOUND

Then User Clicks on Permissions by drop down to select Customer Account#s
PERMISSION DROP DOWN HAS BEEN CLICKED, TO SELECT COMPANY

COMPANY HAS BEEN SELECTED

And User should enter menu "Catalog Search" in search bar to navigate to catalog search
IN ADMIN PAGE

USER IS ON CATALOG SEARCH

Then User should select "Grid layout" in Catalog search layout and disable Do not load full catalog automatically
DONOT AUTO LOAD PODUCT CATALOG DISABLED

DO NOT LOAD FULL CATALOG AUTOMATICALLY, IS DISABLED

And User should save all the details

And User logs out from Admin site, logs in to client credentials
SIGNIN BUTTON CLICKED

ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

USER ICON FOUND

IN ADMIN PAGE

When User is on Home Page
ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

Then User navigate to Client side
USER ICON FOUND

IN ADMIN PAGE

Then User should select Order Entry tab for admin
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderEntry.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

NAVIGATED TO ORDER ENTRY PAGE

Then User selects Account# for Admin side setting
CUSTOMER ACCOUNT# SELECTED IS K12958

NAVIGATED TO ORDER ENTRY PAGE

Then User must click Start Order button for Admin setting testing
NAVIGATED TO ORDER ENTRY PAGE

START BUTTON HAS BEEN CLICKED

Then User should make selection between Pending order or Start New order

Then User should select Note from popup and Order guide from popup
ORDER GUIDE POPUP HAS BEEN FOUND

Then Enter PO# for New order
PO123

NEW ORDER ENTRY PAGE HAS BEEN FOUND

PO# ENTERED IS PO123

Then Click on Add product drop down and select catalog option
ADD PRODUCT BUTTON HAS BEEN CLICKED

ADD PRODUCT FROM CATALOG IS SELECTED

And User should verify products are auto loaded select Product from catalog and Enter Qty for the products
50 60

CATALOG DIALOG BOX HAS BEEN FOUND

DO NOT LOAD FULL CATALOG AUTOMATICALLY,HAS BEEN ENABLED

PORDUCT NUMBER ENERED IN INPUT BOX 0046

PORDUCT NUMBER ENERED IN INPUT BOX 0046

PRODUCT # 0046 PRODUCT QTY 50 60

Then Click on Next button
PRODUCT FOUND IN ORDER ARE

java.lang.AssertionError: expected [true] but found [false] at org.testng.Assert.fail(Assert.java:97) at org.testng.Assert.assertEqualsImpl(Assert.java:136) at org.testng.Assert.assertEquals(Assert.java:118) at org.testng.Assert.assertEquals(Assert.java:751) at org.testng.Assert.assertEquals(Assert.java:761) at pages_DSD_OMS.orderEntry.NewOrderEntryPage.ClickNext(NewOrderEntryPage.java:813) at stepDefination_DSD_OMS.OrderEntryPageSteps.OrderEntryPageSteps.click_on_next_button(OrderEntryPageSteps.java:402) at ✽.Click on Next button(file:///C:/Users/Divya.Ramadas/Documents/Ign/AFS_Automation/OMS_Automation/src/test/resources/features_DSD_OMS/AdminToClientNavigation/orderEntryAdminToClientFeature.feature:244)

And Click on SubmitOrder button
Step skipped

Then User should be navigated to Order Entry page
Step skipped

stepDefination_DSD_OMS.LoginPageStep.afterScenario1(io.cucumber.java.Scenario)
Test scenario for disable auto loading of products in catalog dialog box, in grid view
base64 img

FailTest scenario for disable auto loading of products in catalog dialog box, in grid view

Given User enters URL and is on login page and entered credentials for Admin settings
SIGNIN BUTTON CLICKED

When User is on Home Page for Admin settings
ADMIN PAGE HAS BEEN FOUND

Then User Clicks on Permissions by drop down to select Customer Account#s
PERMISSION DROP DOWN HAS BEEN CLICKED, TO SELECT COMPANY

COMPANY HAS BEEN SELECTED

And User should enter menu "Catalog Search" in search bar to navigate to catalog search
IN ADMIN PAGE

USER IS ON CATALOG SEARCH

Then User should select "Card layout" in Catalog search layout and disable Do not load full catalog automatically
DONOT AUTO LOAD PODUCT CATALOG DISABLED

DO NOT LOAD FULL CATALOG AUTOMATICALLY, IS DISABLED

And User should save all the details

And User logs out from Admin site, logs in to client credentials
SIGNIN BUTTON CLICKED

ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

USER ICON FOUND

IN ADMIN PAGE

When User is on Home Page
ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

Then User navigate to Client side
USER ICON FOUND

IN ADMIN PAGE

Then User should select Order Entry tab for admin
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderEntry.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

NAVIGATED TO ORDER ENTRY PAGE

Then User selects Account# for Admin side setting
CUSTOMER ACCOUNT# SELECTED IS K12958

NAVIGATED TO ORDER ENTRY PAGE

Then User must click Start Order button
NAVIGATED TO ORDER ENTRY PAGE

START BUTTON HAS BEEN CLICKED

Then User should make selection between Pending order or Start New order

Then User should select Note from popup and Order guide from popup
ORDER GUIDE POPUP HAS BEEN FOUND

Then Enter PO# for New order
PO123

NEW ORDER ENTRY PAGE HAS BEEN FOUND

PO# ENTERED IS PO123

Then Click on Add product drop down and select catalog option
ADD PRODUCT BUTTON HAS BEEN CLICKED

ADD PRODUCT FROM CATALOG IS SELECTED

And User should verify products are auto loaded select Product from catalog and Enter Qty for the products
50 60

CATALOG DIALOG BOX HAS BEEN FOUND

DO NOT LOAD FULL CATALOG AUTOMATICALLY,HAS BEEN ENABLED

PRODUCT NUMBER ENTERED IN SEARCH BAR 0046

PRODUCT # 0046 PRODUCT QTY 50 60

Then Click on Next button
PRODUCT FOUND IN ORDER ARE

java.lang.AssertionError: expected [true] but found [false] at org.testng.Assert.fail(Assert.java:97) at org.testng.Assert.assertEqualsImpl(Assert.java:136) at org.testng.Assert.assertEquals(Assert.java:118) at org.testng.Assert.assertEquals(Assert.java:751) at org.testng.Assert.assertEquals(Assert.java:761) at pages_DSD_OMS.orderEntry.NewOrderEntryPage.ClickNext(NewOrderEntryPage.java:813) at stepDefination_DSD_OMS.OrderEntryPageSteps.OrderEntryPageSteps.click_on_next_button(OrderEntryPageSteps.java:402) at ✽.Click on Next button(file:///C:/Users/Divya.Ramadas/Documents/Ign/AFS_Automation/OMS_Automation/src/test/resources/features_DSD_OMS/AdminToClientNavigation/orderEntryAdminToClientFeature1.feature:54)

And Click on SubmitOrder button
Step skipped

Then User should be navigated to Order Entry page
Step skipped

stepDefination_DSD_OMS.LoginPageStep.afterScenario1(io.cucumber.java.Scenario)
Test scenario for disable auto loading of products in catalog dialog box, in grid view
base64 img

FailTest scenario for enable auto loading of products in catalog dialog box, in card view

FailTest scenario for enable auto loading of products in catalog dialog box, in card view

Given User enters URL and is on login page and entered credentials for Admin settings
SIGNIN BUTTON CLICKED

When User is on Home Page for Admin settings
ADMIN PAGE HAS BEEN FOUND

Then User Clicks on Permissions by drop down to select Customer Account#s
PERMISSION DROP DOWN HAS BEEN CLICKED, TO SELECT COMPANY

COMPANY HAS BEEN SELECTED

And User should enter menu "Catalog Search" in search bar to navigate to catalog search
IN ADMIN PAGE

USER IS ON CATALOG SEARCH

Then User should select "Card layout" in Catalog search layout and enable Do not load full catalog automatically
DONOT AUTO LOAD PODUCT CATALOG ENABLED

DO NOT LOAD FULL CATALOG AUTOMATICALLY, IS ENABLED

And User should save all the details

And User logs out from Admin site, logs in to client credentials
SIGNIN BUTTON CLICKED

ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

USER ICON FOUND

IN ADMIN PAGE

When User is on Home Page
ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

Then User navigate to Client side
USER ICON FOUND

IN ADMIN PAGE

Then User should select Order Entry tab for admin
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderEntry.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

NAVIGATED TO ORDER ENTRY PAGE

Then User selects Account# for Admin side setting
CUSTOMER ACCOUNT# SELECTED IS K12958

NAVIGATED TO ORDER ENTRY PAGE

Then User must click Start Order button
NAVIGATED TO ORDER ENTRY PAGE

START BUTTON HAS BEEN CLICKED

Then User should make selection between Pending order or Start New order

Then User should select Note from popup and Order guide from popup
ORDER GUIDE POPUP HAS BEEN FOUND

Then Enter PO# for New order
PO123

NEW ORDER ENTRY PAGE HAS BEEN FOUND

PO# ENTERED IS PO123

Then Click on Add product drop down and select catalog option
ADD PRODUCT BUTTON HAS BEEN CLICKED

ADD PRODUCT FROM CATALOG IS SELECTED

And User should verify products are not auto loaded select Product from catalog and Enter Qty for the products
50 60

CATALOG DIALOG BOX HAS BEEN FOUND

DO NOT LOAD FULL CATALOG AUTOMATICALLY,HAS BEEN ENABLED

PRODUCT NUMBER ENTERED IN SEARCH BAR 0046

PRODUCT # 0046 PRODUCT QTY 50 60

Then Click on Next button
PRODUCT FOUND IN ORDER ARE

java.lang.AssertionError: expected [true] but found [false] at org.testng.Assert.fail(Assert.java:97) at org.testng.Assert.assertEqualsImpl(Assert.java:136) at org.testng.Assert.assertEquals(Assert.java:118) at org.testng.Assert.assertEquals(Assert.java:751) at org.testng.Assert.assertEquals(Assert.java:761) at pages_DSD_OMS.orderEntry.NewOrderEntryPage.ClickNext(NewOrderEntryPage.java:813) at stepDefination_DSD_OMS.OrderEntryPageSteps.OrderEntryPageSteps.click_on_next_button(OrderEntryPageSteps.java:402) at ✽.Click on Next button(file:///C:/Users/Divya.Ramadas/Documents/Ign/AFS_Automation/OMS_Automation/src/test/resources/features_DSD_OMS/AdminToClientNavigation/orderEntryAdminToClientFeature1.feature:26)

And Click on SubmitOrder button
Step skipped

Then User should be navigated to Order Entry page
Step skipped

stepDefination_DSD_OMS.LoginPageStep.afterScenario1(io.cucumber.java.Scenario)
Test scenario for enable auto loading of products in catalog dialog box, in card view
base64 img

FailTest scenario for Use of primary sales rep when submitting orders disabled

FailTest scenario for Use of primary sales rep when submitting orders disabled

Given User should verify admin setting "Use of primary sales rep when submitting orders" is disabled by using "CPUsePrimarySalesRepForNewOrder"
FOR ADMIN SETTING Use of primary sales rep when submitting orders CHANGES

ADMIN SETTING IS ALREADY DISABLED

When User enters URL and is on login page and entered credentials for admin setting
SIGNIN BUTTON CLICKED

When User is on Home Page
ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

Then User navigate to Client side
USER ICON FOUND

IN ADMIN PAGE

Then User should select Order Entry tab for admin
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderEntry.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

NAVIGATED TO ORDER ENTRY PAGE

Then User selects Account# for Admin side setting
CUSTOMER ACCOUNT# SELECTED IS K12958

NAVIGATED TO ORDER ENTRY PAGE

And User should change sales rep other than primary sales rep
PRIMARY SALES REP FOUND IN ORDER ENTRY PAGE IS BF - BF, BRYAN FLINTOFF

SALES REP SELECTED IS BF, BRYAN FLINTOFF

Then User must click Start Order button
NAVIGATED TO ORDER ENTRY PAGE

START BUTTON HAS BEEN CLICKED

Then User should make selection between Pending order or Start New order

Then User should select Note from popup and Order guide from popup
ORDER GUIDE POPUP HAS BEEN FOUND

Then Enter PO# for New order
PO123

NEW ORDER ENTRY PAGE HAS BEEN FOUND

PO# ENTERED IS PO123

And User should verify Sales rep value
SALRES REP VALUE FOUND IN NEW ORDER ENTRY PAGE IS BF, BRYAN FLINTOFF

Then Enter Pro# in Quick Product Entry area

And Check for Case and Unit input box enabled or not based on that enter value
80 70

UOM IS ENABLED AND IT CONTAINS EA VALUE IN IT

UNIT ENTERED FOR QUICK PRODUCT IS 70

Then Click on Next button
PRODUCT FOUND IN ORDER ARE

java.lang.AssertionError: expected [true] but found [false] at org.testng.Assert.fail(Assert.java:97) at org.testng.Assert.assertEqualsImpl(Assert.java:136) at org.testng.Assert.assertEquals(Assert.java:118) at org.testng.Assert.assertEquals(Assert.java:751) at org.testng.Assert.assertEquals(Assert.java:761) at pages_DSD_OMS.orderEntry.NewOrderEntryPage.ClickNext(NewOrderEntryPage.java:813) at stepDefination_DSD_OMS.OrderEntryPageSteps.OrderEntryPageSteps.click_on_next_button(OrderEntryPageSteps.java:402) at ✽.Click on Next button(file:///C:/Users/Divya.Ramadas/Documents/Ign/AFS_Automation/OMS_Automation/src/test/resources/features_DSD_OMS/AdminToClientNavigation/orderEntryAdminToClientFeature1.feature:79)

And Click on SubmitOrder button
Step skipped

Then User should be navigated to Order Entry page
Step skipped

Then User sign out from client side for Admin setting changes
Step skipped

And User should set admin setting "Use of primary sales rep when submitting orders" "CPUsePrimarySalesRepForNewOrder" as default before making changes
Step skipped

stepDefination_DSD_OMS.LoginPageStep.afterScenario1(io.cucumber.java.Scenario)
Test scenario for Use of primary sales rep when submitting orders disabled
base64 img

PassTest scenario for verifying hide zero in product number and enter it in quick product it should be added in grid

PassTest scenario for verifying hide zero in product number and enter it in quick product it should be added in grid

Given User should verify admin setting "Hide leading zeros" is enabled by using "CPGeneralHideLeadingZeros"
ADMIN SETTING FOUND IS0

ADMIN SETTING IS ENABLED

FOR ADMIN SETTING Hide leading zeros CHANGES

ADMIN SETTING IS ENABLED

Then User enters URL and is on login page and entered credentials for admin setting
SIGNIN BUTTON CLICKED

When User is on Home Page
ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

Then User navigate to Client side
USER ICON FOUND

IN ADMIN PAGE

Then User should select Order Entry tab for admin
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderEntry.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

NAVIGATED TO ORDER ENTRY PAGE

Then User selects Account# for Admin side setting
CUSTOMER ACCOUNT# SELECTED IS K12958

NAVIGATED TO ORDER ENTRY PAGE

And User should navigate to Standing Order tab for admin setting
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpStandingOrder.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

And User click on Start standing order button and selects Start date 2 and End date 3 day from current date
STANDING ORDER PAGE HAS BEEN FOUND

START STANDING ORDER BUTTON CLICKED

04/06/2024 HAS BEEN SELECTED AS START DATE FOR STANDING ORDER

04/07/2024 HAS BEEN SELECTED AS START DATE FOR STANDING ORDER

Then User enters Product# in Quick product entry inputbox in admin setting
PRODUCT ENTERED IN QUICK ENTRY WITHOUT PRECEDING ZEROS 78

PRODUCT FOUND IN GRID IS 78

PRODUCT NUMBER ENTERED IN QUICK ENTRY AND GRID ARE SAME AND WITHOUT PRECEDING ZERO

Then User sign out from client side for Admin setting changes

And User should set admin setting "Hide leading zeros" "CPGeneralHideLeadingZeros" as default before making changes
0 WHAT WAS THE PREVIOUS VALUE FOR ADMIN SETTING, AND CURRENT STATUS IS 1

ADMIN SETTING IS DISABLED

FOR ADMIN SETTING Hide leading zeros CHANGES

ADMIN SETTING IS ENABLED

PassTest scenario for verifying hide zero in product number and enter it in quick product it should be added in grid

Given User should verify admin setting "Hide leading zeros" is disabled by using "CPGeneralHideLeadingZeros"
FOR ADMIN SETTING Hide leading zeros CHANGES

ADMIN SETTING IS ALREADY DISABLED

Then User enters URL and is on login page and entered credentials for admin setting
SIGNIN BUTTON CLICKED

When User is on Home Page
ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

Then User navigate to Client side
USER ICON FOUND

IN ADMIN PAGE

Then User should select Order Entry tab for admin
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderEntry.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

NAVIGATED TO ORDER ENTRY PAGE

Then User selects Account# for Admin side setting
CUSTOMER ACCOUNT# SELECTED IS K12958

NAVIGATED TO ORDER ENTRY PAGE

And User should navigate to Standing Order tab for admin setting
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpStandingOrder.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

And User click on Start standing order button and selects Start date 2 and End date 3 day from current date
STANDING ORDER PAGE HAS BEEN FOUND

START STANDING ORDER BUTTON CLICKED

04/06/2024 HAS BEEN SELECTED AS START DATE FOR STANDING ORDER

04/07/2024 HAS BEEN SELECTED AS START DATE FOR STANDING ORDER

Then User enters Product# in Quick product entry inputbox in admin setting for disabling
PRODUCT ENTERED IN QUICK ENTRY WITH PRECEDING ZEROS 0078

PRODUCT FOUND IN GRID IS 0078

PRODUCT NUMBER ENTERED IN QUICK ENTRY AND GRID ARE SAME AND WITH PRECEDING ZERO

Then User sign out from client side for Admin setting changes

And User should set admin setting "Hide leading zeros" "CPGeneralHideLeadingZeros" as default before making changes
0 WHAT WAS THE PREVIOUS VALUE FOR ADMIN SETTING, AND CURRENT STATUS IS 0

FailTest scenario for verifying hide zero in product number and verify it in catalog dialog box

PassTest scenario for verifying hide zero in product number and verify it in catalog dialog box

Given User should verify admin setting "Hide leading zeros" is enabled by using "CPGeneralHideLeadingZeros"
ADMIN SETTING FOUND IS0

ADMIN SETTING IS ENABLED

FOR ADMIN SETTING Hide leading zeros CHANGES

ADMIN SETTING IS ENABLED

Then User enters URL and is on login page and entered credentials for admin setting
SIGNIN BUTTON CLICKED

When User is on Home Page
ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

Then User navigate to Client side
USER ICON FOUND

IN ADMIN PAGE

Then User should select Order Entry tab for admin
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderEntry.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

NAVIGATED TO ORDER ENTRY PAGE

Then User selects Account# for Admin side setting
CUSTOMER ACCOUNT# SELECTED IS K12958

NAVIGATED TO ORDER ENTRY PAGE

And User should navigate to Standing Order tab for admin setting
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpStandingOrder.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

And User click on Start standing order button and selects Start date 2 and End date 3 day from current date
STANDING ORDER PAGE HAS BEEN FOUND

START STANDING ORDER BUTTON CLICKED

04/06/2024 HAS BEEN SELECTED AS START DATE FOR STANDING ORDER

04/07/2024 HAS BEEN SELECTED AS START DATE FOR STANDING ORDER

Then User click on Add Product button in Standing order page and select catalog option

And User checks for catalog popup and searches for product in catalog for admin setting
CATALOG DIALOG BOX HAS BEEN FOUND

Then User sign out from client side for Admin setting changes

And User should set admin setting "Hide leading zeros" "CPGeneralHideLeadingZeros" as default before making changes
0 WHAT WAS THE PREVIOUS VALUE FOR ADMIN SETTING, AND CURRENT STATUS IS 1

ADMIN SETTING IS DISABLED

FOR ADMIN SETTING Hide leading zeros CHANGES

ADMIN SETTING IS ENABLED

FailTest scenario for verifying hide zero in product number and verify it in catalog dialog box

Given User should verify admin setting "Hide leading zeros" is disabled by using "CPGeneralHideLeadingZeros"
FOR ADMIN SETTING Hide leading zeros CHANGES

ADMIN SETTING IS ALREADY DISABLED

Then User enters URL and is on login page and entered credentials for admin setting
SIGNIN BUTTON CLICKED

When User is on Home Page
ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

Then User navigate to Client side
USER ICON FOUND

IN ADMIN PAGE

Then User should select Order Entry tab for admin
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderEntry.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

NAVIGATED TO ORDER ENTRY PAGE

Then User selects Account# for Admin side setting
CUSTOMER ACCOUNT# SELECTED IS K12958

NAVIGATED TO ORDER ENTRY PAGE

And User should navigate to Standing Order tab for admin setting
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpStandingOrder.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

And User click on Start standing order button and selects Start date 2 and End date 3 day from current date
STANDING ORDER PAGE HAS BEEN FOUND

START STANDING ORDER BUTTON CLICKED

04/06/2024 HAS BEEN SELECTED AS START DATE FOR STANDING ORDER

04/07/2024 HAS BEEN SELECTED AS START DATE FOR STANDING ORDER

Then User click on Add Product button in Standing order page and select catalog option

And User checks for catalog popup and searches for product in catalog for admin setting zero preceding product number in OMS env
CATALOG DIALOG BOX HAS BEEN FOUND

java.lang.AssertionError: expected [true] but found [false] at org.testng.Assert.fail(Assert.java:97) at org.testng.Assert.assertEqualsImpl(Assert.java:136) at org.testng.Assert.assertEquals(Assert.java:118) at org.testng.Assert.assertEquals(Assert.java:751) at org.testng.Assert.assertEquals(Assert.java:761) at pages_DSD_OMS.standingOrder.NewStandingOrderPage.cardViewAdminZeroPrecedingOMS(NewStandingOrderPage.java:2153) at stepDefination_DSD_OMS.AdminToClientNavigationSteps.AdminStandingOrderOMSStep.userChecksForCatalogPopupAndSearchesForProductInCatalogForAdminSettingZeroPrecedingProductNumberInOmsEnv(AdminStandingOrderOMSStep.java:50) at ✽.User checks for catalog popup and searches for product in catalog for admin setting zero preceding product number in OMS env(file:///C:/Users/Divya.Ramadas/Documents/Ign/AFS_Automation/OMS_Automation/src/test/resources/features_DSD_OMS/AdminToClientNavigation/standingOrderAdminToClientFeatureOMS.feature:68)

Then User sign out from client side for Admin setting changes
Step skipped

And User should set admin setting "Hide leading zeros" "CPGeneralHideLeadingZeros" as default before making changes
Step skipped

stepDefination_DSD_OMS.LoginPageStep.afterScenario1(io.cucumber.java.Scenario)
Test scenario for verifying hide zero in product number and verify it in catalog dialog box
base64 img

FailTest scenario for verifying functionality of Order submitting message enabling

FailTest scenario for verifying functionality of Order submitting message enabling

Given User should verify admin setting "Hide Order submitting message" is enabled by using "CPHideOrderSubmittingMessage"
ADMIN SETTING FOUND IS0

ADMIN SETTING IS ENABLED

FOR ADMIN SETTING Hide Order submitting message CHANGES

ADMIN SETTING IS ENABLED

When User enters URL and is on login page and entered credentials for admin setting
SIGNIN BUTTON CLICKED

When User is on Home Page
ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

Then User navigate to Client side
USER ICON FOUND

IN ADMIN PAGE

Then User should select Order Entry tab for admin
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderEntry.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

NAVIGATED TO ORDER ENTRY PAGE

Then User selects Account# for Admin side setting
CUSTOMER ACCOUNT# SELECTED IS K12958

NAVIGATED TO ORDER ENTRY PAGE

Then User must click Start Order button
NAVIGATED TO ORDER ENTRY PAGE

START BUTTON HAS BEEN CLICKED

Then User should make selection between Pending order or Start New order

Then User should select Note from popup and Order guide from popup
ORDER GUIDE POPUP HAS BEEN FOUND

Then Enter PO# for New order
PO123

NEW ORDER ENTRY PAGE HAS BEEN FOUND

PO# ENTERED IS PO123

Then Enter Pro# in Quick Product Entry area

And Check for Case and Unit input box enabled or not based on that enter value
80 70

UOM IS ENABLED AND IT CONTAINS EA VALUE IN IT

UNIT ENTERED FOR QUICK PRODUCT IS 70

Then Click on Next button
PRODUCT FOUND IN ORDER ARE

java.lang.AssertionError: expected [true] but found [false] at org.testng.Assert.fail(Assert.java:97) at org.testng.Assert.assertEqualsImpl(Assert.java:136) at org.testng.Assert.assertEquals(Assert.java:118) at org.testng.Assert.assertEquals(Assert.java:751) at org.testng.Assert.assertEquals(Assert.java:761) at pages_DSD_OMS.orderEntry.NewOrderEntryPage.ClickNext(NewOrderEntryPage.java:813) at stepDefination_DSD_OMS.OrderEntryPageSteps.OrderEntryPageSteps.click_on_next_button(OrderEntryPageSteps.java:402) at ✽.Click on Next button(file:///C:/Users/Divya.Ramadas/Documents/Ign/AFS_Automation/OMS_Automation/src/test/resources/features_DSD_OMS/AdminToClientNavigation/webOrderingAdminToClientFeature.feature:21)

And Click on SubmitOrder button to verify error message on submitting
Step skipped

Then User should be navigated to Order Entry page and verify the error submitting message
Step skipped

Then User sign out from client side for Admin setting changes
Step skipped

And User should set admin setting "Hide Order submitting message" "CPHideOrderSubmittingMessage" as default before making changes
Step skipped

stepDefination_DSD_OMS.LoginPageStep.afterScenario1(io.cucumber.java.Scenario)
Test scenario for verifying functionality of Order submitting message enabling
base64 img

FailTest scenario for verifying functionality of Order submitting message enabling

Given User should verify admin setting "Hide Order submitting message" is disabled by using "CPHideOrderSubmittingMessage"
ADMIN SETTING IS DISABLED

FOR ADMIN SETTING Hide Order submitting message CHANGES

ADMIN SETTING IS DISABLED

When User enters URL and is on login page and entered credentials for admin setting
SIGNIN BUTTON CLICKED

When User is on Home Page
ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

Then User navigate to Client side
USER ICON FOUND

IN ADMIN PAGE

Then User should select Order Entry tab for admin
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderEntry.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

NAVIGATED TO ORDER ENTRY PAGE

Then User selects Account# for Admin side setting
CUSTOMER ACCOUNT# SELECTED IS K12958

NAVIGATED TO ORDER ENTRY PAGE

Then User must click Start Order button
NAVIGATED TO ORDER ENTRY PAGE

START BUTTON HAS BEEN CLICKED

Then User should make selection between Pending order or Start New order

Then User should select Note from popup and Order guide from popup
ORDER GUIDE POPUP HAS BEEN FOUND

Then Enter PO# for New order
PO123

NEW ORDER ENTRY PAGE HAS BEEN FOUND

PO# ENTERED IS PO123

Then Enter Pro# in Quick Product Entry area

And Check for Case and Unit input box enabled or not based on that enter value
80 70

UOM IS ENABLED AND IT CONTAINS EA VALUE IN IT

UNIT ENTERED FOR QUICK PRODUCT IS 70

Then Click on Next button
PRODUCT FOUND IN ORDER ARE

java.lang.AssertionError: expected [true] but found [false] at org.testng.Assert.fail(Assert.java:97) at org.testng.Assert.assertEqualsImpl(Assert.java:136) at org.testng.Assert.assertEquals(Assert.java:118) at org.testng.Assert.assertEquals(Assert.java:751) at org.testng.Assert.assertEquals(Assert.java:761) at pages_DSD_OMS.orderEntry.NewOrderEntryPage.ClickNext(NewOrderEntryPage.java:813) at stepDefination_DSD_OMS.OrderEntryPageSteps.OrderEntryPageSteps.click_on_next_button(OrderEntryPageSteps.java:402) at ✽.Click on Next button(file:///C:/Users/Divya.Ramadas/Documents/Ign/AFS_Automation/OMS_Automation/src/test/resources/features_DSD_OMS/AdminToClientNavigation/webOrderingAdminToClientFeature.feature:46)

And Click on SubmitOrder button
Step skipped

Then User should be navigated to Order Entry page and verify the error submitting message is not displayed
Step skipped

Then User sign out from client side for Admin setting changes
Step skipped

And User should set admin setting "Hide Order submitting message" "CPHideOrderSubmittingMessage" as default before making changes
Step skipped

stepDefination_DSD_OMS.LoginPageStep.afterScenario1(io.cucumber.java.Scenario)
Test scenario for verifying functionality of Order submitting message enabling
base64 img
scenarios for admin credentials and client credentials, for Order Factor related test scenarios

5:08:42 pm / 00:19:15:995 Fail

scenarios for admin credentials and client credentials, for Order Factor related test scenarios
04.04.2024 5:08:42 pm 04.04.2024 5:27:58 pm 00:19:15:995 · #test-id=2,918

FailTest scenario for adding product to order factor

FailTest scenario for adding product to order factor

Given User enters URL and is on login page and entered credentials for Admin settings
SIGNIN BUTTON CLICKED

When User is on Home Page for Admin settings
ADMIN PAGE HAS BEEN FOUND

Then User Clicks on Permissions by drop down to select Customer Account#s
PERMISSION DROP DOWN HAS BEEN CLICKED, TO SELECT COMPANY

COMPANY HAS BEEN SELECTED

And User should enter menu "Order Entry" in search bar to navigate to order entry search
IN ADMIN PAGE

ADMIN PAGE HAS BEEN FOUND

Then User should navigate to "Order factor/Order increments" from horizontal menu to select Order factor, select order factor level "Order factor by customer and product"
ORDER FACTOR PAGE HAS BEEN FOUND

ORDER FACTOR LEVEL SELECTED IS Order factor by customer and product

And User should add product to order factor list and add "5"
NO PRODUCTS HAS BEEN FOUND

PRODUCT DIALOG BOX HAS BEEN FOUND

PRODUCT FOUND

java.lang.AssertionError: expected [true] but found [false] at org.testng.Assert.fail(Assert.java:97) at org.testng.Assert.assertEqualsImpl(Assert.java:136) at org.testng.Assert.assertEquals(Assert.java:118) at org.testng.Assert.assertEquals(Assert.java:751) at org.testng.Assert.assertEquals(Assert.java:761) at pages_DSD_OMS.orderFactorAdmin.orderFactorAdminPage.validateAddingOfProductInOrderFactorGrid(orderFactorAdminPage.java:364) at stepDefination_DSD_OMS.AdminToClientNavigationSteps.OrderFactorAdminStep.userShouldAddProductToOrderFactorListAndAdd(OrderFactorAdminStep.java:89) at ✽.User should add product to order factor list and add "5"(file:///C:/Users/Divya.Ramadas/Documents/Ign/AFS_Automation/OMS_Automation/src/test/resources/features_DSD_OMS/AdminToClientNavigation/orderFactorOrderEntryFeature.feature:12)

And User should save all the details
Step skipped

And User logs out from Admin site
Step skipped

stepDefination_DSD_OMS.LoginPageStep.afterScenario1(io.cucumber.java.Scenario)
Test scenario for adding product to order factor
base64 img

FailTest scenario for adding product to order factor

Given User enters URL and is on login page and entered credentials for Admin settings
SIGNIN BUTTON CLICKED

When User is on Home Page for Admin settings
ADMIN PAGE HAS BEEN FOUND

Then User Clicks on Permissions by drop down to select Customer Account#s
PERMISSION DROP DOWN HAS BEEN CLICKED, TO SELECT COMPANY

COMPANY HAS BEEN SELECTED

And User should enter menu "Order Entry" in search bar to navigate to order entry search
IN ADMIN PAGE

ADMIN PAGE HAS BEEN FOUND

Then User should navigate to "Order factor/Order increments" from horizontal menu to select Order factor, select order factor level "Order factor by customer and product"
ORDER FACTOR PAGE HAS BEEN FOUND

ORDER FACTOR LEVEL SELECTED IS Order factor by customer and product

And User should delete product from order factor list
java.lang.AssertionError: expected [true] but found [false] at org.testng.Assert.fail(Assert.java:97) at org.testng.Assert.assertEqualsImpl(Assert.java:136) at org.testng.Assert.assertEquals(Assert.java:118) at org.testng.Assert.assertEquals(Assert.java:751) at org.testng.Assert.assertEquals(Assert.java:761) at pages_DSD_OMS.orderFactorAdmin.orderFactorAdminPage.validateAddingOfProductInOrderFactorGrid(orderFactorAdminPage.java:364) at stepDefination_DSD_OMS.AdminToClientNavigationSteps.OrderFactorAdminStep.userShouldDeleteProductFromOrderFactorList(OrderFactorAdminStep.java:165) at ✽.User should delete product from order factor list(file:///C:/Users/Divya.Ramadas/Documents/Ign/AFS_Automation/OMS_Automation/src/test/resources/features_DSD_OMS/AdminToClientNavigation/orderFactorOrderEntryFeature.feature:47)

And User should save all the details
Step skipped

And User logs out from Admin site
Step skipped

stepDefination_DSD_OMS.LoginPageStep.afterScenario1(io.cucumber.java.Scenario)
Test scenario for adding product to order factor
base64 img

PassTest scenario for adding product to order factor

Given User enters URL and is on login page and entered credentials for Admin settings
SIGNIN BUTTON CLICKED

When User is on Home Page for Admin settings
ADMIN PAGE HAS BEEN FOUND

Then User Clicks on Permissions by drop down to select Customer Account#s
PERMISSION DROP DOWN HAS BEEN CLICKED, TO SELECT COMPANY

COMPANY HAS BEEN SELECTED

And User should enter menu "Order Entry" in search bar to navigate to order entry search
IN ADMIN PAGE

ADMIN PAGE HAS BEEN FOUND

Then User should navigate to "Order factor/Order increments" from horizontal menu to select Order factor, select order factor level "Order factor at product master level"
ORDER FACTOR PAGE HAS BEEN FOUND

ORDER FACTOR LEVEL SELECTED IS Order factor at product master level

And User should add product to order factor list and add "5"
PRODUCT HAS BEEN FOUND

And User should save all the details

And User logs out from Admin site

PassTest scenario for adding product to order factor

Given User enters URL and is on login page and entered credentials for Admin settings
SIGNIN BUTTON CLICKED

When User is on Home Page for Admin settings
ADMIN PAGE HAS BEEN FOUND

Then User Clicks on Permissions by drop down to select Customer Account#s
PERMISSION DROP DOWN HAS BEEN CLICKED, TO SELECT COMPANY

COMPANY HAS BEEN SELECTED

And User should enter menu "Order Entry" in search bar to navigate to order entry search
IN ADMIN PAGE

ADMIN PAGE HAS BEEN FOUND

Then User should navigate to "Order factor/Order increments" from horizontal menu to select Order factor, select order factor level "Order factor at product master level"
ORDER FACTOR PAGE HAS BEEN FOUND

ORDER FACTOR LEVEL SELECTED IS Order factor at product master level

And User should delete product from order factor list

And User should save all the details

And User logs out from Admin site

FailTest scenario for verifying order factor at product master level

Given User enters URL and is on login page and entered credentials
SIGNIN BUTTON CLICKED

When User is on Home Page
ADMIN PAGE OR ORDER ENTRY PAGE HAS BEEN FOUND

Then User navigate to Client side
USER ICON FOUND

IN ADMIN PAGE

Then User should select Order Entry tab for admin
https://ignitionqaerp.afsi.com/omsi/clientportal/apps/cpOrderEntry.html?p=QJFsTz5JBfVNODvKd%2b4hK5iehkJNvWapcrevP50HxzU%3d

NAVIGATED TO ORDER ENTRY PAGE

Then User selects Account# for Inventory for admin setting
CUSTOMER ACCOUNT# SELECTED IS K12958

Then User must click Start Order button
NAVIGATED TO ORDER ENTRY PAGE

START BUTTON HAS BEEN CLICKED

Then User should make selection between Pending order or Start New order

Then User should select Note from popup and Order guide from popup
ORDER GUIDE POPUP HAS BEEN FOUND

Then Enter PO# for New order
PO123

NEW ORDER ENTRY PAGE HAS BEEN FOUND

PO# ENTERED IS PO123

Then Enter Pro# in Quick Product Entry area for Order factor

And Check for Case and Unit input box enabled or not based on that enter value for qty to verify order factor
java.lang.NullPointerException: Cannot invoke "String.equalsIgnoreCase(String)" because "uomString" is null at stepDefination_DSD_OMS.AdminToClientNavigationSteps.OrderFactorAdminStep.checkForCaseAndUnitInputBoxEnabledOrNotBasedOnThatEnterValueForQtyToVerifyOrderFactor(OrderFactorAdminStep.java:107) at ✽.Check for Case and Unit input box enabled or not based on that enter value for qty to verify order factor(file:///C:/Users/Divya.Ramadas/Documents/Ign/AFS_Automation/OMS_Automation/src/test/resources/features_DSD_OMS/AdminToClientNavigation/orderFactorOrderEntryFeature.feature:32)

Then Enter Pro# in Quick Product Entry area
Step skipped

And Check for Case and Unit input box enabled or not based on that enter value
4 4

Step skipped

Then Click on Next button and validate order factor dialog box
Step skipped

And Click on SubmitOrder button
Step skipped

Then User should be navigated to Order Entry page
Step skipped

stepDefination_DSD_OMS.LoginPageStep.afterScenario1(io.cucumber.java.Scenario)
Test scenario for verifying order factor at product master level
base64 img

FailTest scenario for verifying order factor at product master level

FailTest scenario for verifying order factor at product master level

Given User enters URL and is on login page and entered credentials for Admin settings
SIGNIN BUTTON CLICKED

When User is on Home Page for Admin settings
ADMIN PAGE HAS BEEN FOUND

Then User Clicks on Permissions by drop down to select Customer Account#s
PERMISSION DROP DOWN HAS BEEN CLICKED, TO SELECT COMPANY

COMPANY HAS BEEN SELECTED

And User should enter menu "Order Entry" in search bar to navigate to catalog search
IN ADMIN PAGE

java.lang.AssertionError: expected [true] but found [false] at org.testng.Assert.fail(Assert.java:97) at org.testng.Assert.assertEqualsImpl(Assert.java:136) at org.testng.Assert.assertEquals(Assert.java:118) at org.testng.Assert.assertEquals(Assert.java:751) at org.testng.Assert.assertEquals(Assert.java:761) at pages_DSD_OMS.adminCatalogSearch.catalogSearchPage.validateCatalogSearchPage(catalogSearchPage.java:54) at stepDefination_DSD_OMS.AdminToClientNavigationSteps.AdminOrderEntryStep.userShouldEnterMenuInSearchBarToNavigateToCatalogSearch(AdminOrderEntryStep.java:332) at ✽.User should enter menu "Order Entry" in search bar to navigate to catalog search(file:///C:/Users/Divya.Ramadas/Documents/Ign/AFS_Automation/OMS_Automation/src/test/resources/features_DSD_OMS/AdminToClientNavigation/orderFactorOrderEntryFeature.feature:73)

Then User should navigate to "Order factor/Order increments" from horizontal menu to select Order factor, select order factor level "Order factor at product master level" and get product#
Step skipped

And User should save all the details
Step skipped

And User logs out from Admin site, logs in to client credentials
Step skipped

When User is on Home Page
Step skipped

Then User navigate to Client side
Step skipped

Then User should select Order Entry tab for admin
Step skipped

Then User selects Account# for Inventory for admin setting
Step skipped

Then User must click Start Order button
Step skipped

Then User should make selection between Pending order or Start New order
Step skipped

Then User should select Note from popup and Order guide from popup
Step skipped

Then Enter PO# for New order
PO123

Step skipped

Then Enter Pro# in Quick Product Entry area for Order factor
Step skipped

And Check for Case and Unit input box enabled or not based on that enter value for qty to verify order factor
Step skipped

Then Enter Pro# in Quick Product Entry area
Step skipped

And Check for Case and Unit input box enabled or not based on that enter value
4 4

Step skipped

Then Click on Next button and validate order factor dialog box
Step skipped

And Click on SubmitOrder button
Step skipped

Then User should be navigated to Order Entry page
Step skipped

stepDefination_DSD_OMS.LoginPageStep.afterScenario1(io.cucumber.java.Scenario)
Test scenario for verifying order factor at product master level
base64 img

Exception

java.lang.NullPointerException

1 tests

java.lang.NullPointerException

1 failed

Status	Timestamp	TestName
Fail	17:13:25 pm	And Check for Case and Unit input box enabled or not based on that enter value for qty to verify order factor scenarios for admin credentials and client credentials, for Order Factor related test scenarios.Test scenario for verifying order factor at product master level.And Check for Case and Unit input box enabled or not based on that enter value for qty to verify order factor

java.lang.AssertionError

20 tests

java.lang.AssertionError

20 failed

Status	Timestamp	TestName
Fail	15:57:09 pm	Then Check for Catalog popup and check for price column in catalog in Disconnected mode scenarios for admin credentials and client credentials.Test scenario for enabling Hide prices in offline mode.Then Check for Catalog popup and check for price column in catalog in Disconnected mode
Fail	15:58:47 pm	Then User must be on Order Entry Page in disconnected mode scenarios for admin credentials and client credentials.Test scenario for disabling Hide prices in offline mode.Then User must be on Order Entry Page in disconnected mode
Fail	16:30:29 pm	Then Click on Next button scenarios for admin credentials and client credentials.Test scenario to verify functionality when orders exist before order submission is disabled.Then Click on Next button
Fail	16:34:44 pm	Then Click on Next button scenarios for admin credentials and client credentials.Test scenario to verify functionality when orders exist before order submission is enabled.Then Click on Next button
Fail	16:38:01 pm	Then Click on Next button scenarios for admin credentials and client credentials.Test scenario to verify functionality when orders exist before order submission is enabled and click on cancel button, in Order exists dialog box.Then Click on Next button
Fail	16:40:53 pm	Then Click on Next button scenarios for admin credentials and client credentials.Test scenario to verify functionality when orders exist before order submission is enabled and click on No button, in Order exists dialog box.Then Click on Next button
Fail	16:43:48 pm	Then Click on Next button scenarios for admin credentials and client credentials.Test scenario to verify functionality for enable admin setting for PO#.Then Click on Next button
Fail	16:46:26 pm	Then Click on Next button scenarios for admin credentials and client credentials.Test scenario to verify functionality for disabled admin setting for PO#.Then Click on Next button
Fail	16:51:11 pm	Then Click on Next button scenarios for admin credentials and client credentials.Test scenario to enable multiple orders per delivery day.Then Click on Next button
Fail	16:54:43 pm	Then Click on Next button scenarios for admin credentials and client credentials.Test scenario for enable auto loading of products in catalog dialog box, in grid view.Then Click on Next button
Fail	16:58:13 pm	Then Click on Next button scenarios for admin credentials and client credentials.Test scenario for disable auto loading of products in catalog dialog box, in grid view.Then Click on Next button
Fail	17:01:42 pm	Then Click on Next button scenarios for admin credentials and client credentials.Test scenario for enable auto loading of products in catalog dialog box, in card view.Then Click on Next button
Fail	17:05:03 pm	Then Click on Next button scenarios for admin credentials and client credentials.Test scenario for disable auto loading of products in catalog dialog box, in grid view.Then Click on Next button
Fail	17:07:24 pm	Then Click on Next button scenarios for admin credentials and client credentials.Test scenario for Use of primary sales rep when submitting orders disabled.Then Click on Next button
Fail	17:11:06 pm	And User should add product to order factor list and add "5" scenarios for admin credentials and client credentials, for Order Factor related test scenarios.Test scenario for adding product to order factor.And User should add product to order factor list and add "5"
Fail	17:17:00 pm	And User should delete product from order factor list scenarios for admin credentials and client credentials, for Order Factor related test scenarios.Test scenario for adding product to order factor.And User should delete product from order factor list
Fail	17:22:21 pm	And User should enter menu "Order Entry" in search bar to navigate to catalog search scenarios for admin credentials and client credentials, for Order Factor related test scenarios.Test scenario for verifying order factor at product master level.And User should enter menu "Order Entry" in search bar to navigate to catalog search
Fail	17:38:53 pm	And User checks for catalog popup and searches for product in catalog for admin setting zero preceding product number in OMS env scenarios for admin credentials and client credentials.Test scenario for verifying hide zero in product number and verify it in catalog dialog box.And User checks for catalog popup and searches for product in catalog for admin setting zero preceding product number in OMS env
Fail	17:41:19 pm	Then Click on Next button scenarios for admin credentials and client credentials.Test scenario for verifying functionality of Order submitting message enabling.Then Click on Next button
Fail	17:43:57 pm	Then Click on Next button scenarios for admin credentials and client credentials.Test scenario for verifying functionality of Order submitting message enabling.Then Click on Next button

Category

@DeleteOrderFactorCustomer

1 tests

@DeleteOrderFactorCustomer

1 failed

Status	Timestamp	TestName
Fail	17:14:31 pm	Test scenario for adding product to order factor scenarios for admin credentials and client credentials, for Order Factor related test scenarios.Test scenario for adding product to order factor

1 1

@HidePriceDisable

2 tests

@HidePriceDisable

1 passed 1 failed

Status	Timestamp	TestName
Fail	15:58:18 pm	Test scenario for disabling Hide prices in offline mode scenarios for admin credentials and client credentials.Test scenario for disabling Hide prices in offline mode
Pass	16:00:26 pm	Test scenario for validating Catalog is loading automatically or not scenarios for admin credentials and client credentials.Test scenario for validating Catalog is loading automatically or not

@AdminSecurityEnablingSettings

1 tests

@AdminSecurityEnablingSettings

1 passed

Status	Timestamp	TestName
Pass	15:42:20 pm	Test scenario for verifing admin security scenario, to Enable admin setting and verify in client side scenarios for admin credentials and client credentials.Test scenario for verifing admin security scenario, to Enable admin setting and verify in client side

@CatalogDonotAutoLoadDisableCardView

1 tests

@CatalogDonotAutoLoadDisableCardView

1 failed

Status	Timestamp	TestName
Fail	17:02:58 pm	Test scenario for disable auto loading of products in catalog dialog box, in grid view scenarios for admin credentials and client credentials.Test scenario for disable auto loading of products in catalog dialog box, in grid view

@CatalogProductsAutomaticLoadDisabled

1 tests

@CatalogProductsAutomaticLoadDisabled

1 passed

Status	Timestamp	TestName
Pass	15:46:14 pm	Test scenario for validating Catalog is loading automatically or not scenarios for admin credentials and client credentials.Test scenario for validating Catalog is loading automatically or not

@AdminSecurityDisableSettings

1 tests

@AdminSecurityDisableSettings

1 passed

Status	Timestamp	TestName
Pass	15:38:22 pm	Test scenario for verifing admin security scenario, to disable admin setting and verify in client side scenarios for admin credentials and client credentials.Test scenario for verifing admin security scenario, to disable admin setting and verify in client side

@SkipReasonCode

1 tests

@SkipReasonCode

1 passed

Status	Timestamp	TestName
Pass	16:14:50 pm	Test scenario for verifying admin setting for OCL, For skip reason enable and disable scenarios for admin credentials and client credentials.Test scenario for verifying admin setting for OCL, For skip reason enable and disable

@ExistingOrderFoundDisabled

1 tests

@ExistingOrderFoundDisabled

1 failed

Status	Timestamp	TestName
Fail	16:29:05 pm	Test scenario to verify functionality when orders exist before order submission is disabled scenarios for admin credentials and client credentials.Test scenario to verify functionality when orders exist before order submission is disabled

@CatalogDonotAutoLoadEnableCardView

2 tests

@CatalogDonotAutoLoadEnableCardView

2 failed

Status	Timestamp	TestName
Fail	16:59:31 pm	Test scenario for enable auto loading of products in catalog dialog box, in card view scenarios for admin credentials and client credentials.Test scenario for enable auto loading of products in catalog dialog box, in card view
Fail	17:02:58 pm	Test scenario for disable auto loading of products in catalog dialog box, in grid view scenarios for admin credentials and client credentials.Test scenario for disable auto loading of products in catalog dialog box, in grid view

@DisablingSalesHelp

1 tests

@DisablingSalesHelp

1 passed

Status	Timestamp	TestName
Pass	16:05:16 pm	Test scenario for verifying functionality of Non Presence of Sales help scenarios for admin credentials and client credentials.Test scenario for verifying functionality of Non Presence of Sales help

@DisableMultipleOrder

1 tests

@DisableMultipleOrder

1 passed

Status	Timestamp	TestName
Pass	16:47:44 pm	Test scenario to disable Multiple orders per delivery day scenarios for admin credentials and client credentials.Test scenario to disable Multiple orders per delivery day

1 2

@AddOrderFactorCustomer

3 tests

@AddOrderFactorCustomer

1 passed 2 failed

Status	Timestamp	TestName
Fail	17:08:42 pm	Test scenario for adding product to order factor scenarios for admin credentials and client credentials, for Order Factor related test scenarios.Test scenario for adding product to order factor
Fail	17:14:31 pm	Test scenario for adding product to order factor scenarios for admin credentials and client credentials, for Order Factor related test scenarios.Test scenario for adding product to order factor
Pass	17:18:05 pm	Test scenario for adding product to order factor scenarios for admin credentials and client credentials, for Order Factor related test scenarios.Test scenario for adding product to order factor

@EnableMultipleOrder

1 tests

@EnableMultipleOrder

1 failed

Status	Timestamp	TestName
Fail	16:49:54 pm	Test scenario to enable multiple orders per delivery day scenarios for admin credentials and client credentials.Test scenario to enable multiple orders per delivery day

@DeleteOrderFactorProductMaster

1 tests

@DeleteOrderFactorProductMaster

1 passed

Status	Timestamp	TestName
Pass	17:25:10 pm	Test scenario for adding product to order factor scenarios for admin credentials and client credentials, for Order Factor related test scenarios.Test scenario for adding product to order factor

@DisablingeCommerceHelp

1 tests

@DisablingeCommerceHelp

1 passed

Status	Timestamp	TestName
Pass	16:07:52 pm	Test scenario for verifying functionality of Non Presence of eCommerce scenarios for admin credentials and client credentials.Test scenario for verifying functionality of Non Presence of eCommerce

@ExistingOrderFoundEnabled

1 tests

@ExistingOrderFoundEnabled

1 failed

Status	Timestamp	TestName
Fail	16:31:53 pm	Test scenario to verify functionality when orders exist before order submission is enabled scenarios for admin credentials and client credentials.Test scenario to verify functionality when orders exist before order submission is enabled

@DisableHideOrderSubmittingMessage

1 tests

@DisableHideOrderSubmittingMessage

1 failed

Status	Timestamp	TestName
Fail	17:42:42 pm	Test scenario for verifying functionality of Order submitting message enabling scenarios for admin credentials and client credentials.Test scenario for verifying functionality of Order submitting message enabling

@PrimarySalesRepSubmittingOrdersEnable

1 tests

@PrimarySalesRepSubmittingOrdersEnable

1 failed

Status	Timestamp	TestName
Fail	17:06:20 pm	Test scenario for Use of primary sales rep when submitting orders disabled scenarios for admin credentials and client credentials.Test scenario for Use of primary sales rep when submitting orders disabled

@EnablePO

1 tests

@EnablePO

1 failed

Status	Timestamp	TestName
Fail	16:42:16 pm	Test scenario to verify functionality for enable admin setting for PO# scenarios for admin credentials and client credentials.Test scenario to verify functionality for enable admin setting for PO#

@HidePriceEnabled

1 tests

@HidePriceEnabled

1 failed

Status	Timestamp	TestName
Fail	15:49:44 pm	Test scenario for enabling Hide prices in offline mode scenarios for admin credentials and client credentials.Test scenario for enabling Hide prices in offline mode

@StandingOrderHideZeroInCatalogDisable

1 tests

@StandingOrderHideZeroInCatalogDisable

1 failed

Status	Timestamp	TestName
Fail	17:37:42 pm	Test scenario for verifying hide zero in product number and verify it in catalog dialog box scenarios for admin credentials and client credentials.Test scenario for verifying hide zero in product number and verify it in catalog dialog box

2 1

@StandingOrderHideZeroInCatalogEnable

3 tests

@StandingOrderHideZeroInCatalogEnable

2 passed 1 failed

Status	Timestamp	TestName
Pass	17:31:43 pm	Test scenario for verifying hide zero in product number and verify it in catalog dialog box scenarios for admin credentials and client credentials.Test scenario for verifying hide zero in product number and verify it in catalog dialog box
Pass	17:34:53 pm	Test scenario for verifying hide zero in product number and enter it in quick product it should be added in grid scenarios for admin credentials and client credentials.Test scenario for verifying hide zero in product number and enter it in quick product it should be added in grid
Fail	17:37:42 pm	Test scenario for verifying hide zero in product number and verify it in catalog dialog box scenarios for admin credentials and client credentials.Test scenario for verifying hide zero in product number and verify it in catalog dialog box

@OrderTakerDisableAndPrintButtonVerification

1 tests

@OrderTakerDisableAndPrintButtonVerification

1 passed

Status	Timestamp	TestName
Pass	16:20:44 pm	Test scenario for verifying order taker admin setting scenarios for admin credentials and client credentials.Test scenario for verifying order taker admin setting

@CallDesk

1 tests

@CallDesk

1 passed

Status	Timestamp	TestName
Pass	16:18:09 pm	Test scenario for verifying call desk existance scenarios for admin credentials and client credentials.Test scenario for verifying call desk existance

@EnableHideOrderSubmittingMessage

2 tests

@EnableHideOrderSubmittingMessage

2 failed

Status	Timestamp	TestName
Fail	17:40:07 pm	Test scenario for verifying functionality of Order submitting message enabling scenarios for admin credentials and client credentials.Test scenario for verifying functionality of Order submitting message enabling
Fail	17:42:42 pm	Test scenario for verifying functionality of Order submitting message enabling scenarios for admin credentials and client credentials.Test scenario for verifying functionality of Order submitting message enabling

@CatalogDonotAutoLoadEnableGridView

1 tests

@CatalogDonotAutoLoadEnableGridView

1 failed

Status	Timestamp	TestName
Fail	16:52:30 pm	Test scenario for enable auto loading of products in catalog dialog box, in grid view scenarios for admin credentials and client credentials.Test scenario for enable auto loading of products in catalog dialog box, in grid view

@eCommerceHelp

1 tests

@eCommerceHelp

1 passed

Status	Timestamp	TestName
Pass	16:12:37 pm	Test scenario for handling eCommerce drop down scenarios for admin credentials and client credentials.Test scenario for handling eCommerce drop down

@SalesHelp

1 tests

@SalesHelp

1 passed

Status	Timestamp	TestName
Pass	16:10:31 pm	Test scenario for handling Sales help from drop down scenarios for admin credentials and client credentials.Test scenario for handling Sales help from drop down

1 1

@OrderFactorProductMasterLevel

2 tests

@OrderFactorProductMasterLevel

1 passed 1 failed

Status	Timestamp	TestName
Fail	17:21:47 pm	Test scenario for verifying order factor at product master level scenarios for admin credentials and client credentials, for Order Factor related test scenarios.Test scenario for verifying order factor at product master level
Pass	17:25:10 pm	Test scenario for adding product to order factor scenarios for admin credentials and client credentials, for Order Factor related test scenarios.Test scenario for adding product to order factor

@InventoryCatalogEnabled

1 tests

@InventoryCatalogEnabled

1 passed

Status	Timestamp	TestName
Pass	16:02:47 pm	Test scenario for enabled admin setting and verifying catalog dialog box is loaded with products scenarios for admin credentials and client credentials.Test scenario for enabled admin setting and verifying catalog dialog box is loaded with products

@StandingOrderHideZeroEnable

1 tests

@StandingOrderHideZeroEnable

1 passed

Status	Timestamp	TestName
Pass	17:29:06 pm	Test scenario for verifying hide zero in product number and enter it in quick product it should be added in grid scenarios for admin credentials and client credentials.Test scenario for verifying hide zero in product number and enter it in quick product it should be added in grid

@OrderTakerEnableVerifyRoute

1 tests

@OrderTakerEnableVerifyRoute

1 passed

Status	Timestamp	TestName
Pass	16:23:44 pm	Test scenario for verifying order taker admin setting and verify route details in client side scenarios for admin credentials and client credentials.Test scenario for verifying order taker admin setting and verify route details in client side

@ExistingOrderFoundNo

1 tests

@ExistingOrderFoundNo

1 failed

Status	Timestamp	TestName
Fail	16:39:24 pm	Test scenario to verify functionality when orders exist before order submission is enabled and click on No button, in Order exists dialog box scenarios for admin credentials and client credentials.Test scenario to verify functionality when orders exist before order submission is enabled and click on No button, in Order exists dialog box

@OrderFactorCustomer

1 tests

@OrderFactorCustomer

1 failed

Status	Timestamp	TestName
Fail	17:12:26 pm	Test scenario for verifying order factor at product master level scenarios for admin credentials and client credentials, for Order Factor related test scenarios.Test scenario for verifying order factor at product master level

@AddOrderFactorProductMaster

1 tests

@AddOrderFactorProductMaster

1 passed

Status	Timestamp	TestName
Pass	17:18:05 pm	Test scenario for adding product to order factor scenarios for admin credentials and client credentials, for Order Factor related test scenarios.Test scenario for adding product to order factor

@DisablePO

1 tests

@DisablePO

1 failed

Status	Timestamp	TestName
Fail	16:45:12 pm	Test scenario to verify functionality for disabled admin setting for PO# scenarios for admin credentials and client credentials.Test scenario to verify functionality for disabled admin setting for PO#

@OrderTakerDisableVerifyRoute

1 tests

@OrderTakerDisableVerifyRoute

1 passed

Status	Timestamp	TestName
Pass	16:26:26 pm	Test scenario for verifying order taker disabled in admin setting and verify route details in client side scenarios for admin credentials and client credentials.Test scenario for verifying order taker disabled in admin setting and verify route details in client side

@StandingOrderHideZeroDisable

1 tests

@StandingOrderHideZeroDisable

1 passed

Status	Timestamp	TestName
Pass	17:34:53 pm	Test scenario for verifying hide zero in product number and enter it in quick product it should be added in grid scenarios for admin credentials and client credentials.Test scenario for verifying hide zero in product number and enter it in quick product it should be added in grid

@InventoryCatalogDisabled

1 tests

@InventoryCatalogDisabled

1 passed

Status	Timestamp	TestName
Pass	16:00:26 pm	Test scenario for validating Catalog is loading automatically or not scenarios for admin credentials and client credentials.Test scenario for validating Catalog is loading automatically or not

@ExistingOrderFoundCancel

1 tests

@ExistingOrderFoundCancel

1 failed

Status	Timestamp	TestName
Fail	16:36:36 pm	Test scenario to verify functionality when orders exist before order submission is enabled and click on cancel button, in Order exists dialog box scenarios for admin credentials and client credentials.Test scenario to verify functionality when orders exist before order submission is enabled and click on cancel button, in Order exists dialog box

@CatalogDonotAutoLoadDisableGridView

1 tests

@CatalogDonotAutoLoadDisableGridView

1 failed

Status	Timestamp	TestName
Fail	16:56:00 pm	Test scenario for disable auto loading of products in catalog dialog box, in grid view scenarios for admin credentials and client credentials.Test scenario for disable auto loading of products in catalog dialog box, in grid view

Started

Apr 4, 2024 03:38:02 pm

Ended

Apr 4, 2024 05:45:01 pm

Features Passed

0

Features Failed

2

Features

0 features passed

2 features failed, 0 skipped, 0 others

Scenarios

20 scenarios passed

21 scenarios failed, 0 skipped, 0 others

Steps

475 steps passed

21 steps failed, 99 skipped, 0 others

Timeline

scenarios for admin credentials and client credentials

scenarios for admin credentials and client credentials, for Order Factor related test scenarios

java.lang.NullPointerException

java.lang.AssertionError

@DeleteOrderFactorCustomer

@HidePriceDisable

@AdminSecurityEnablingSettings

@CatalogDonotAutoLoadDisableCardView

@CatalogProductsAutomaticLoadDisabled

@AdminSecurityDisableSettings

@SkipReasonCode

@ExistingOrderFoundDisabled

@CatalogDonotAutoLoadEnableCardView

@DisablingSalesHelp

@DisableMultipleOrder

@AddOrderFactorCustomer

@EnableMultipleOrder

@DeleteOrderFactorProductMaster

@DisablingeCommerceHelp

@ExistingOrderFoundEnabled

@DisableHideOrderSubmittingMessage

@PrimarySalesRepSubmittingOrdersEnable

@EnablePO

@HidePriceEnabled

@StandingOrderHideZeroInCatalogDisable

@StandingOrderHideZeroInCatalogEnable

@OrderTakerDisableAndPrintButtonVerification

@CallDesk

@EnableHideOrderSubmittingMessage

@CatalogDonotAutoLoadEnableGridView

@eCommerceHelp

@SalesHelp

@OrderFactorProductMasterLevel

@InventoryCatalogEnabled

@StandingOrderHideZeroEnable

@OrderTakerEnableVerifyRoute

@ExistingOrderFoundNo

@OrderFactorCustomer

@AddOrderFactorProductMaster

@DisablePO

@OrderTakerDisableVerifyRoute

@StandingOrderHideZeroDisable

@InventoryCatalogDisabled

@ExistingOrderFoundCancel

@CatalogDonotAutoLoadDisableGridView

Apr 4, 2024 03:38:02 pm

Apr 4, 2024 05:45:01 pm

0

2

Features

Scenarios

Steps